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":["@carnesen/[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":["@carnesen/[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
Scripts11
buildtsc --project tsconfig.build.jsonbuild:cleanrimraf lib && npm run buildlinttslint --project .lint:fixnpm run lint -- --fixpostversionnpm publishpreversionnpm test && npm run build:cleantestnpm run lint && npm run test:unit && npm run buildtest:unitjest --forceExit srctest:unit:coveragenpm run test:unit -- --coveragetest:unit:coverage:watchnpm run test:unit -- --coverage --watchtest:unit:watchnpm run test:unit -- --watch
Dependencies3
@carnesen/bitcoin-config0.0.0-4@types/signal-exit3.0.0signal-exit3.0.2