← Home

@polkadot-api/json-rpc-provider-proxy

npm Repository Homepage
15
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

volivajosepot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): voliva is a well-established polkadot-api contributor (59 approved packages) publishing from the official monorepo CI with SLSA provenance. This is a legitimate team rotation, not a takeover. ai
publish-pattern dormant-publish AI (publish-pattern): This is a sub-package in the polkadot-api monorepo; long dormancy reflects no need for changes, not abandonment. SLSA provenance confirms the publish originated from the official repo. ai

Versions (showing 15 of 15)

Version Deps Published
0.4.1 0 / 1
0.4.0 0 / 1
0.3.1 0 / 1
0.3.0 0 / 1
0.2.8 0 / 1
0.2.7 0 / 1
0.2.6 0 / 1
0.2.5 0 / 1
0.2.4 0 / 1
0.2.3 0 / 1
0.2.2 0 / 1
0.2.1 0 / 1
0.2.0 0 / 1
0.1.0 0 / 1
0.0.1 0 / 1

v0.4.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: voliva → GitHub Actions (on unknown date, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (voliva) on unknown date, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.