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
- 563
- Versions published
- 54
- First published
- May 2026
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["[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":["[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 1 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/core/handoff-record.js | matched "aws_access_key" | 5 |
Manifest
Package metadata
Scripts30
buildnode -e "require('fs').rmSync('dist',{recursive:true,force:true})" && tsc -p tsconfig.jsoncheckbun run check:package && bun run test:fullcheck:core:nodenode scripts/run-node-core-check.mjscheck:installnpm run check:pack && node --test tests/integration/*.test.jscheck:packnpm pack --dry-run --jsoncheck:packagenode -e "const fs=require('fs'); JSON.parse(fs.readFileSync('package.json','utf8')); console.log('package.json ok')"check:typechecktsc -p tsconfig.json --noEmitdocs:buildbun run --cwd docs-site builddocs:checkbun run --cwd docs-site checkdocs:check:fastbun run --cwd docs-site check:fastdocs:devbun run --cwd docs-site devdocs:previewbun run --cwd docs-site previewprepacknpm run buildprepublishOnlynpm run release:checkrelease:checknpm run check && npm run docs:check && npm run check:installtestbun run test:fulltest:auditnode scripts/audit-tests.mjs --jsontest:clinode scripts/run-cli-tests.mjs --build clitest:coveragenode scripts/run-cli-tests.mjs --build coveragetest:fastnode scripts/run-cli-tests.mjs --build fasttest:fast:nodenode scripts/run-cli-tests.mjs --build-runner=npm fasttest:fullnode scripts/run-cli-tests.mjs --build full-autotest:full:autonode scripts/run-cli-tests.mjs --build full-autotest:full:profilenode scripts/run-cli-tests.mjs --build full-profiletest:full:serialnode scripts/run-cli-tests.mjs --build fulltest:relatednode scripts/run-cli-tests.mjs --build relatedtest:related:cachednode scripts/run-cli-tests.mjs related-cachedtest:related:profilenode scripts/run-cli-tests.mjs --build related-profiletest:releasenode scripts/run-cli-tests.mjs --build releasetest:release:nodenode scripts/run-cli-tests.mjs --build-runner=npm release
Dependencies2
smol-toml^1.6.1sql.js^1.14.1