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
- May 2021
- Publisher
- fivetanley-heroku
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":["@heroku/[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/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "AWS_ACCESS_KEY"
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 5 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/lib/aws.js | matched "AWS_ACCESS_KEY" | 5 |
Manifest
Package metadata
Scripts9
buildrm -rf lib && tscchangelogconventional-changelog -p angular -i CHANGELOG.md -s -r 0 && git add CHANGELOG.mdlinteslint . --ext .ts --config .eslintrcpostpackrm -f oclif.manifest.jsonposttestyarn lintprepackyarn build && node ./bin/run manifestpretestyarn build --noEmit && echo 'Skipping test dir compile check in CI for now (3rd party type error) but you should compile it locally'testmocha --forbid-only "test/**/*.test.ts"versionnpm run changelog && node ./bin/run readme && git add README.md
Dependencies19
@oclif/command^1.8.0@oclif/config^1.17.0@oclif/errors^1.3.3@oclif/plugin-help^3.2.0cli-ux^5.2.1debug^4.1.1execa^5.0.0find-yarn-workspace-root^2.0.0fs-extra^8.1github-slugger^1.2.1lodash^4.17.11normalize-package-data^3.0.0qqjs^0.3.10stream.pipeline-shim^1.1.0tar^6.1.0tmp^0.2.1tslib^2.0.3which^2.0.2workerpool^6.1.0