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
- 16Established · −30% score
- First published
- Feb 2023
- Publisher
- jannuom
Effective trust discount applied: −30% (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
Remote Payload: matched "raw.githubusercontent.com"
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 8 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/dist/core/registry-fetch.js | matched "raw.githubusercontent.com" | 12 |
Manifest
Package metadata
Scripts14
analyzenode scripts/package-info.jsbuildtscdevtsc -wlinteslint . --ext .ts --max-warnings 200lint:fixeslint . --ext .ts --fixpostbuildchmod +x dist/index.jsprepublishOnlynpm run buildrelease:checknpm run build && npm pack --dry-runrelease:majornpm version major -m 'Release v%s' && npm publish && git push --follow-tagsrelease:minornpm version minor -m 'Release v%s' && npm publish && git push --follow-tagsrelease:patchnpm version patch -m 'Release v%s' && npm publish && git push --follow-tagsrelease:testnpm run build && npm pack && echo 'Test the .tgz file before publishing'sizenpm pack --dry-run 2>&1 | grep -E 'package size|Tarball Contents'size:fullnpm pack --dry-run
Dependencies11
boxen^8.0.1chalk^5.6.2cli-table3^0.6.5commander^14.0.1execa^9.6.0figlet^1.9.3gradient-string^3.0.0ora^9.0.0prompts^2.4.2update-notifier^7.3.1zod^4.1.12