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
- Mar 2025
- Publisher
- bhsd
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 "curl "
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/download.sh | matched "curl " | 12 |
Manifest
Package metadata
Scripts10
buildtsc && mv dist/* . && npm run bundle && esbuild reports/src/*.ts --charset=utf8 --bundle --minify --target=es2019 --format=iife --sourcemap --outdir=reports/dist && rm reports/dist/common.js*bundleesbuild reports/src/*.ts --charset=utf8 --bundle --format=esm --outdir=build && rm build/common.jslintnpm run lint:ts && npm run lint:css && npm run lint:mdlint:cssstylelint --cache reports/*.csslint:mdmarkdownlint-cli2 '**/*.md'lint:tstsc --noEmit && tsc --project reports/tsconfig.json --noEmit && eslint --cache .lsnpm i --package-lock-only && npm ls --package-lock-only --all --omit=devprepublishOnlynpm run buildstartnode server.jstoolforgebash scan-toolforge.sh
Dependencies2
@bhsd/nodejs^1.0.1wikilint^2.43.0