@polkadot-api/substrate-client
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): voliva is an established polkadot-api contributor (21 approved packages, 566 days history); SLSA attestation confirms CI/CD build from official repo, ruling out account compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms the release originated from the official polkadot-api CI pipeline; dormancy reflects release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@polkadot-api/utils | AI (dependencies): First-party sibling package from the same polkadot-api monorepo; unvetted status reflects pipeline gap, not genuine risk. | ai | |
| dependencies | unvetted-dep:@polkadot-api/raw-client | AI (dependencies): First-party sibling package from the same polkadot-api monorepo; unvetted status reflects pipeline gap, not genuine risk. | ai | |
| dependencies | unvetted-dep:@polkadot-api/json-rpc-provider | AI (dependencies): First-party sibling package from the same polkadot-api monorepo; unvetted status reflects pipeline gap, not genuine risk. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 3 / 0 | |
| 0.6.0 | 3 / 0 | |
| 0.5.0 | 3 / 0 | |
| 0.4.7 | 3 / 0 | |
| 0.4.6 | 3 / 0 | |
| 0.4.5 | 3 / 0 | |
| 0.4.4 | 3 / 0 | |
| 0.4.3 | 3 / 0 | |
| 0.4.2 | 3 / 0 | |
| 0.4.1 | 2 / 0 | |
| 0.4.0 | 2 / 0 | |
| 0.3.0 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 2 / 0 | |
| 0.1.4 | 2 / 0 | |
| 0.1.3 | 1 / 1 | |
| 0.1.2 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 2 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 0 / 2 |
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-04-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.