Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Weekly downloads
- 268
- Versions published
- 32
- First published
- Apr 2026
- Publisher
- akaoio
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@akaoio/[email protected]"],"fail_on":"review"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@akaoio/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "AWS_ACCESS_KEY"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk review · score 20 · status changed
Evidence
Static findings
4 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 4 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/lib/rs3.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/lib/rs3.min.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/lib/s3.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/lib/s3.min.js | matched "AWS_ACCESS_KEY" | 5 |
Manifest
Package metadata
Scripts49
benchnode --experimental-vm-modules test/bench/run.jsbench:base62node --experimental-vm-modules test/bench/07_base62.jsbench:dupnode --experimental-vm-modules test/bench/03_dup.jsbench:hamnode --experimental-vm-modules test/bench/05_ham.jsbench:hashnode --experimental-vm-modules test/bench/01_hash.jsbench:jsonnode --experimental-vm-modules test/bench/02_json.jsbench:radixnode --experimental-vm-modules test/bench/04_radix.jsbench:signnode --experimental-vm-modules test/bench/06_crypto_sign.jsbuildnpm run build:releasebuild:chainsnode lib/builder/chains.jsbuild:cryptonode lib/builder/crypto.jsbuild:pennode lib/builder/pen.jsbuild:releasenpm run build:zen && npm run minifybuild:zennpm run build:pen && npm run build:crypto && node lib/builder/zen.js && npm run minify:zencleannode clean.jsdebugnode --prof-process --preprocess -j isolate*.log > v8data.json && rm isolate*.log && echo 'drag & drop ./v8data.json into https://mapbox.github.io/flamebearer/'dockerhooks/builde2emocha e2e/distributed.jsformatprettier --write .httpsHTTPS_KEY=test/https/server.key HTTPS_CERT=test/https/server.crt npm startmcp:devnode lib/mcp.jsmcp:testnetZEN_NET=testnet node lib/mcp.jsminifynode lib/minify.jsminify:zenterser zen.js --module -o zen.min.js --compress --mangleprepublishOnlynpm run verify:releasestartnode script/server.jsstart:profnode --prof script/server.jstestnpm run build:zen && npm run test:alltest:allnode test/all.jstest:browserplaywright test- …and 19 more.