Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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
No high-signal static finding in the saved report.
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 low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts8
doctornpm run publish:checkfix:permissionsnode tools/fix-permissions.mjspack:drynpm pack --dry-runprepublishOnlynpm run validate:productionpublish:checknode tools/fix-permissions.mjs --quiet && node bin/aoc.mjs publish-check --pack-dry-runtestnode tools/fix-permissions.mjs --quiet && PYTHONDONTWRITEBYTECODE=1 python3 tests/aggressive_validation.pytest:npm-clinode tools/fix-permissions.mjs --quiet && PYTHONDONTWRITEBYTECODE=1 node tests/npm_cli_validation.mjsvalidate:productionnode tools/fix-permissions.mjs --quiet && npm test && npm run publish:check && npm pack --dry-run