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
- 152
- Versions published
- 4
- First published
- Apr 2025
- Publisher
- hypery2k
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":["@continuoussecuritytooling/[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":["@continuoussecuritytooling/[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
buildtsccleannpm ci && rimraf distlinteslint "src/**/*.*s" "test/**/*.js"prettier:checkprettier --list-different "./**/*.{json,yaml,js,ts}"prettier:writeprettier --write "./**/*.{json,yaml,js,ts}"testnpm run lint && npm run test-covtest-covnyc npm run test-spectest-speccross-env TS_NODE_PROJECT=test/tsconfig.json mocha -r ts-node/register "test/**/*.spec.{ts,js}" -R spec
Dependencies7
ajv^8.0.0fast-json-patch^3.0.0glob^11.0.0js-yaml^3.14.0json-schema-migrate^2.0.0json5^2.1.3minimist^1.2.0