@polkadot-api/observable-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 | missing-githead | AI (provenance): Package has SLSA provenance attestation via Sigstore CI/CD, which provides stronger supply chain integrity than gitHead. Missing gitHead is a pipeline artifact, not a security signal for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by legitimate maintainer transition; SLSA provenance attestation confirms official CI/CD pipeline was used, ruling out account takeover. | ai | |
| provenance | publisher-changed | AI (provenance): voliva has 56 approved / 0 rejected packages and 566 days of ecosystem history; SLSA provenance confirms CI/CD publication. Legitimate team transition within polkadot-api. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package with proper repository metadata and TypeScript exports; missing description is not a malware indicator here. | ai | |
| dependencies | unvetted-dep:@polkadot-api/substrate-client | AI (dependencies): Sibling package within the polkadot-api monorepo; same trusted publisher and SLSA-attested release pipeline. | ai | |
| dependencies | unvetted-dep:@polkadot-api/substrate-bindings | AI (dependencies): Sibling package within the polkadot-api monorepo; same trusted publisher and SLSA-attested release pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo sub-package; sparse README/metadata is expected for library components not intended for standalone discovery. | ai | |
| dependencies | unvetted-dep:@polkadot-api/utils | AI (dependencies): Sibling package within the polkadot-api monorepo; same trusted publisher and SLSA-attested release pipeline. | ai | |
| dependencies | unvetted-dep:@polkadot-api/metadata-builders | AI (dependencies): Sibling package within the polkadot-api monorepo; same trusted publisher and SLSA-attested release pipeline. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 0.18.7 | 4 / 2 | |
| 0.18.6 | 4 / 2 | |
| 0.18.5 | 4 / 2 | |
| 0.18.4 | 4 / 2 | |
| 0.18.3 | 4 / 2 | |
| 0.18.2 | 4 / 2 | |
| 0.18.1 | 4 / 2 | |
| 0.18.0 | 4 / 2 | |
| 0.17.3 | 4 / 2 | |
| 0.17.2 | 4 / 2 | |
| 0.17.1 | 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.2 | 4 / 2 | |
| 0.15.1 | 4 / 2 | |
| 0.15.0 | 4 / 2 | |
| 0.14.1 | 4 / 2 | |
| 0.14.0 | 4 / 2 | |
| 0.13.8 | 4 / 2 | |
| 0.13.7 | 4 / 2 | |
| 0.13.6 | 4 / 2 | |
| 0.13.5 | 3 / 2 | |
| 0.13.4 | 3 / 2 | |
| 0.13.3 | 3 / 2 | |
| 0.13.2 | 3 / 2 | |
| 0.13.1 | 3 / 2 | |
| 0.13.0 | 3 / 2 | |
| 0.12.0 | 3 / 2 | |
| 0.11.2 | 3 / 2 | |
| 0.11.1 | 3 / 2 | |
| 0.11.0 | 3 / 2 | |
| 0.10.2 | 3 / 2 | |
| 0.10.1 | 3 / 2 | |
| 0.10.0 | 3 / 2 | |
| 0.9.1 | 3 / 2 | |
| 0.9.0 | 3 / 2 | |
| 0.8.6 | 3 / 2 | |
| 0.8.5 | 3 / 2 | |
| 0.8.4 | 3 / 2 | |
| 0.8.3 | 3 / 2 | |
| 0.8.2 | 3 / 2 | |
| 0.8.1 | 3 / 2 | |
| 0.8.0 | 3 / 2 | |
| 0.7.2 | 3 / 2 | |
| 0.7.1 | 3 / 2 |
v0.18.7
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.18.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. 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.1
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.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished 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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: josepot.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: josepot.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.