PkgRadar

Package evidence

@akaoio/[email protected]

Credential file access: matched "AWS_ACCESS_KEY"

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.

Versions published
29
First published
Apr 2026
Publisher
akaoio

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarballAdd to CI gate
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"}'
Publisherakaoio
Artifact bytes891,861
Previous version1.0.30
Published2026-05-21T09:15:28.216Z
SHA-256ea3946ead2abed6ed807383c170b1f3e536fc2a87db72d174e4364a0155b9b4d

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

review
Last checked
reviewRisk
20Score
1.0.31Version
Status history (2 events)
  1. available → available · risk review · score 20 · status available -> available, risk high -> review, score 50 -> 20
  2. new → available · risk high · score 50 · 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)
SeverityKindPathDetailPoints
lowCredential file accesspackage/lib/rs3.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/lib/rs3.min.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/lib/s3.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/lib/s3.min.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts49
  • benchnode --experimental-vm-modules test/bench/run.js
  • bench:base62node --experimental-vm-modules test/bench/07_base62.js
  • bench:dupnode --experimental-vm-modules test/bench/03_dup.js
  • bench:hamnode --experimental-vm-modules test/bench/05_ham.js
  • bench:hashnode --experimental-vm-modules test/bench/01_hash.js
  • bench:jsonnode --experimental-vm-modules test/bench/02_json.js
  • bench:radixnode --experimental-vm-modules test/bench/04_radix.js
  • bench:signnode --experimental-vm-modules test/bench/06_crypto_sign.js
  • buildnpm run build:release
  • build:chainsnode lib/builder/chains.js
  • build:cryptonode lib/builder/crypto.js
  • build:pennode lib/builder/pen.js
  • build:releasenpm run build:zen && npm run minify
  • build:zennpm run build:pen && npm run build:crypto && node lib/builder/zen.js && npm run minify:zen
  • cleannode clean.js
  • debugnode --prof-process --preprocess -j isolate*.log > v8data.json && rm isolate*.log && echo 'drag & drop ./v8data.json into https://mapbox.github.io/flamebearer/'
  • dockerhooks/build
  • e2emocha e2e/distributed.js
  • formatprettier --write .
  • httpsHTTPS_KEY=test/https/server.key HTTPS_CERT=test/https/server.crt npm start
  • mcp:devnode lib/mcp.js
  • mcp:testnetZEN_NET=testnet node lib/mcp.js
  • minifynode lib/minify.js
  • minify:zenterser zen.js --module -o zen.min.js --compress --mangle
  • prepublishOnlynpm run verify:release
  • startnode script/server.js
  • start:profnode --prof script/server.js
  • testnpm run build:zen && npm run test:all
  • test:allnode test/all.js
  • test:browserplaywright test
  • …and 19 more.