← Home

nanomessage-rpc

npm Repository Homepage

Tiny rpc on top of nanomessage

2
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tinchoz49

Keywords

rpcnanomessagegeut

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Mature GEUT ecosystem package with 26 versions and 6+ years of history; lack of provenance is expected for packages predating Sigstore adoption. ai

Versions (showing 2 of 2)

Version Deps Published
5.0.1 7 / 7
5.0.0 7 / 7

v5.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.