Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":["@openhoo/[email protected]"],"fail_on":"high"}'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":["@openhoo/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Credential file access: matched "GITHUB_TOKEN"
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 high · score 60 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential file access | package/dist/cli.js | matched "GITHUB_TOKEN" | 30 |
| high | Credential file access | package/actions/release/action.yml | matched "GITHUB_TOKEN" | 30 |
Manifest
Package metadata
Scripts9
buildbun build src/cli.ts --target=bun --format=esm --outfile=dist/cli.js && chmod +x dist/cli.jscheckbun run typecheck && bun test && bun run builddevbun run src/cli.tsplanbun run src/cli.ts planprepackbun run buildreleasebun run src/cli.ts releasesync:actionsbun run scripts/sync-action-versions.tstestbun testtypechecktsc --noEmit