@polkadot/util-keyring
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): bs58 is a well-known Base58 encoding library appropriate for a keyring/crypto utility in the Polkadot ecosystem. Addition is contextually expected and not suspicious. | ai | |
| source-diff | encoded-string-file:index.spec.js | AI (source-diff): Long encoded string is a JSON keystore test fixture in a spec file, used to verify cryptographic parsing. This is standard practice for Polkadot-JS crypto libraries and poses no runtime risk. | ai | |
| phantom-deps | phantom-dep:@types/bs58 | AI (phantom-deps): @types/bs58 is a TypeScript type definition package; it is legitimately declared as a dependency for type resolution and not directly imported in source. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm by years; absence of provenance is expected and not a risk signal for this established polkadot-js package. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 5 / 0 | |
| 0.24.9 | 5 / 0 | |
| 0.24.8 | 5 / 0 | |
| 0.24.7 | 5 / 0 | |
| 0.24.6 | 5 / 0 | |
| 0.24.3 | 5 / 0 | |
| 0.23.2 | 4 / 0 | |
| 0.23.1 | 4 / 0 | |
| 0.22.11 | 4 / 0 | |
| 0.22.10 | 4 / 0 | |
| 0.22.9 | 4 / 0 | |
| 0.22.8 | 4 / 0 | |
| 0.22.7 | 4 / 0 | |
| 0.22.6 | 4 / 0 | |
| 0.22.5 | 4 / 0 | |
| 0.22.4 | 4 / 0 | |
| 0.22.3 | 4 / 0 | |
| 0.22.2 | 4 / 0 | |
| 0.22.1 | 4 / 0 | |
| 0.21.3 | 4 / 0 | |
| 0.21.2 | 4 / 0 | |
| 0.21.1 | 4 / 0 | |
| 0.20.5 | 4 / 0 | |
| 0.20.4 | 4 / 0 | |
| 0.20.3 | 4 / 0 | |
| 0.20.2 | 4 / 0 | |
| 0.19.9 | 4 / 0 | |
| 0.19.8 | 4 / 0 | |
| 0.19.7 | 4 / 0 | |
| 0.19.6 | 4 / 0 | |
| 0.19.5 | 4 / 0 | |
| 0.19.4 | 3 / 0 | |
| 0.19.3 | 3 / 0 | |
| 0.19.2 | 3 / 0 | |
| 0.19.1 | 3 / 0 | |
| 0.18.6 | 3 / 0 | |
| 0.18.5 | 3 / 0 | |
| 0.18.4 | 3 / 0 | |
| 0.18.3 | 3 / 0 | |
| 0.18.2 | 3 / 0 | |
| 0.18.1 | 3 / 0 | |
| 0.17.4 | 3 / 0 | |
| 0.17.3 | 3 / 0 | |
| 0.17.2 | 3 / 0 | |
| 0.17.1 | 3 / 0 | |
| 0.16.6 | 3 / 0 | |
| 0.16.5 | 3 / 0 | |
| 0.16.4 | 3 / 0 | |
| 0.16.3 | 3 / 0 | |
| 0.16.2 | 3 / 0 | |
| 0.16.1 | 3 / 0 |
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.