← Home

@exodus/asset-json-rpc

npm Repository Homepage
4
Versions
—
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

joshuabot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org-internal roster rotation for @exodus scoped package, not a compromise indicator. ai
maintainer-change maintainer-removed AI (maintainer-change): Same org roster churn; publisher track record is clean. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is Exodus's own @exodus/fetch, replacing third-party wretch. ai

Versions (showing 4 of 4)

Version Deps Published
2.1.0 1 / 0
2.0.2 1 / 0
2.0.1 1 / 0
2.0.0 1 / 0

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.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.