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
- 999
- Versions published
- 12
- First published
- May 2026
- Publisher
- gael55x
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 5 · 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/security/secret-scan.js | matched "aws_access_key" | 5 |
Manifest
Package metadata
Scripts26
architecture:checknode scripts/check-architecture-boundaries.mjsbenchnode benchmarks/scripts/run-benchmarks.mjsbench:comparatorsnode benchmarks/scripts/run-comparator.mjsbench:post-betanode benchmarks/scripts/run-post-beta-baseline.mjs --artifact published-betabench:post-beta:localnode benchmarks/scripts/run-post-beta-baseline.mjs --artifact local-candidatebench:summarynode benchmarks/scripts/summarize-results.mjsbenchmark:runnode scripts/run-benchmark-suite.mjsbeta:checknpm run check && npm run benchmark:run && npm run e2e:alpha && npm run test:connectbeta:client-trialnpm run test:connectbuildtsc -p tsconfig.dist.jsonbuild:testtsc -p tsconfig.build.jsonchecknpm run docs:check && npm run fixtures:check && npm run memory:check && npm run architecture:check && npm run storage:check && npm run typecheck && npm run package:check && npm run install:check && npm run test:behaviordocs:checknode scripts/check-docs-structure.mjs && node scripts/check-examples.mjse2e:alphanode scripts/e2e-alpha-smoke.mjsfixtures:checknode scripts/check-fixtures.mjsglobal:smokenode scripts/check-global-install-smoke.mjsinstall:checknode scripts/check-install-smoke.mjsmemory:checknode scripts/check-in-memory-loop.mjspackage:checknpm run build && node scripts/check-package.mjspostbuildnode scripts/copy-storage-migrations.mjsprebuildnode scripts/clean-dist.mjsprepacknpm run buildstorage:checknode scripts/check-storage-migrations.mjstest:behaviornode scripts/clean-test-build.mjs && npm run build:test && node scripts/run-behavior-tests.mjstest:connectnode scripts/run-beta-client-trial.mjstypechecktsc --noEmit
Dependencies1
typescript5.9.3