k-rpc
Low-level implementation of the k-rpc protocol used the BitTorrent DHT.
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
ferossmafintosh
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in example.js is a hardcoded 20-byte DHT node ID — standard for BitTorrent DHT implementations. Not a malicious payload; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:k-bucket | AI (dependencies): k-bucket is a well-known mafintosh package (same author as k-rpc) used for DHT routing tables. Unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:k-rpc-socket | AI (dependencies): k-rpc-socket is a well-known mafintosh package (same author as k-rpc) for DHT socket communication. Unvetted status is a pipeline artifact. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 3 / 2 |
v5.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.