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
- 7
- First published
- Jan 2025
- Publisher
- noahnu
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":["@noahnu/[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":["@noahnu/[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
Scripts4
cleanrun workspace:clean "$(pwd)"prepackrun workspace:build "$(pwd)"run-localrun -T tsx ./src/bin.tsrun-local-debugrun -T tsx --inspect-brk ./src/bin.ts
Dependencies11
@types/debug^4.1.12@yarnpkg/cli^4.10.3@yarnpkg/core^4.4.4@yarnpkg/fslib^3.1.3@yarnpkg/plugin-essentials^4.4.4@yarnpkg/plugin-git^3.1.3clipanion^4.0.0-rc.4debug^4.4.3micromatch^4.0.8semver^7.7.3typanion^3.14.0