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
- 4
- First published
- May 2026
- Publisher
- andre-p
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":["@cello-protocol/[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":["@cello-protocol/[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
Scripts 2
Sign in to view install / lifecycle script contents.
Dependencies19
@cello-protocol/crypto0.0.8@cello-protocol/protocol-types0.0.5@chainsafe/libp2p-noise^17.0.0@chainsafe/libp2p-yamux^8.0.1@libp2p/autonat3.0.20@libp2p/circuit-relay-v2^4.2.3@libp2p/crypto^5.0.0@libp2p/dcutr^3.0.18@libp2p/identify^4.1.3@libp2p/interface^3.0.0@libp2p/peer-id^6.0.0@libp2p/tcp^11.0.18@libp2p/websockets^10.1.11@multiformats/multiaddr^13.0.0@noble/curves2.2.0it-length-prefixed^10.0.1it-pipe^3.0.1libp2p^3.2.3uint8arrays^5.1.1