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
- 8
- First published
- Aug 2019
- Publisher
- chadian
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":["@heroku-cli/[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":["@heroku-cli/[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
Scripts5
postpackrm -f oclif.manifest.jsonposttesttslint -p test -t stylishprepackrm -rf lib && tsc -b && oclif-dev manifest && oclif-dev readmetestnyc --extension .ts mocha --forbid-only "test/**/*.test.ts"versionoclif-dev readme && git add README.md
Dependencies8
@heroku-cli/color^1.1.14@heroku-cli/command^8.2.6@oclif/command^1.5.8@oclif/config^1.10.4@oclif/errors^1.2.2@types/supports-color^5.3.0cli-ux^5.0.0tslib^1.9.3