@polkadot-api/substrate-bindings
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 publisher (70 approved/0 rejected) within the polkadot-api org; the transition from josepot is a legitimate team handoff, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): The @polkadot-api ecosystem has 688 registry versions; dormancy in this sub-package reflects versioning cadence, not abandonment. SLSA provenance further mitigates takeover risk. | ai | |
| dependencies | unvetted-dep:scale-ts | AI (dependencies): scale-ts is a well-known SCALE codec library used throughout the Polkadot/Substrate JS ecosystem; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@polkadot-api/utils | AI (dependencies): @polkadot-api/utils is a sibling package in the same polkadot-api monorepo; expected internal dependency, not a risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are normal for scoped internal packages in a large monorepo. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo sub-package; missing description is a cosmetic issue, not a security signal for this well-established package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.20.3 | 4 / 2 | |
| 0.20.2 | 4 / 2 | |
| 0.20.1 | 4 / 2 | |
| 0.20.0 | 4 / 2 | |
| 0.19.0 | 4 / 2 | |
| 0.18.0 | 4 / 2 | |
| 0.17.0 | 4 / 2 | |
| 0.16.6 | 4 / 2 | |
| 0.16.5 | 4 / 2 | |
| 0.16.4 | 4 / 2 | |
| 0.16.3 | 4 / 2 | |
| 0.16.2 | 4 / 2 | |
| 0.16.1 | 4 / 2 | |
| 0.16.0 | 4 / 2 | |
| 0.15.1 | 4 / 2 | |
| 0.15.0 | 4 / 2 | |
| 0.14.0 | 4 / 2 | |
| 0.13.0 | 4 / 2 | |
| 0.12.0 | 4 / 2 | |
| 0.11.1 | 4 / 2 | |
| 0.11.0 | 4 / 2 | |
| 0.10.0 | 4 / 2 | |
| 0.9.4 | 4 / 2 | |
| 0.9.3 | 4 / 2 | |
| 0.9.2 | 4 / 2 | |
| 0.9.1 | 4 / 2 | |
| 0.9.0 | 4 / 2 | |
| 0.8.0 | 4 / 2 | |
| 0.7.0 | 4 / 2 | |
| 0.6.3 | 4 / 2 | |
| 0.6.2 | 4 / 2 | |
| 0.6.1 | 4 / 2 | |
| 0.6.0 | 4 / 2 | |
| 0.5.0 | 4 / 2 | |
| 0.4.0 | 4 / 2 | |
| 0.3.0 | 4 / 2 | |
| 0.2.0 | 4 / 2 | |
| 0.1.0 | 4 / 2 | |
| 0.0.1 | 4 / 2 |
v0.20.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-19. 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.18.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.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
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-23. This could indicate a legitimate maintainer transition or an account compromise.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.