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
- 101
- First published
- Jan 2026
- Publisher
- marcus.pousette
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":["@peerbit/[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":["@peerbit/[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
Scripts6
buildaegir build --no-bundlecleanaegir cleanlintaegir linttestaegir test --target nodetest:covaegir test -t node --covtest:e2epnpm --dir ./e2e test
Dependencies10
@dao-xyz/borsh^6.0.0@dao-xyz/borsh-rpc^2.0.5@peerbit/canonical-client1.1.34@peerbit/canonical-host1.0.40@peerbit/document13.0.44@peerbit/document-interface3.2.42@peerbit/indexer-interface3.0.4@peerbit/program6.0.31@peerbit/shared-log-proxy2.0.43@peerbit/stream-interface6.0.10