@polkadot/keyring
Keyring management
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:pair/toJson.spec.js | AI (source-diff): Test fixture containing hex-encoded ed25519 keypair data for keyring unit tests; expected for a crypto key management library. | ai | |
| phantom-deps | phantom-dep:@types/bs58 | AI (phantom-deps): TypeScript type declarations for the bs58 runtime dependency; loaded by the TS compiler, not directly imported at runtime. | ai | |
| source-diff | encoded-string-file:index.spec.js | AI (source-diff): Long string is a hex-encoded PKCS8 test fixture in a keyring test file — expected for this package's domain. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transition from polkadotjs to paritytech-ci (Parity Technologies CI account). paritytech-ci has strong track record: 605 approved, 0 rejected. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): paritytech-ci is Parity Technologies' CI account, the organization behind Polkadot. Expected maintainer for this ecosystem. | ai |
Versions (showing 100 of 312)
| Version | Deps | Published |
|---|---|---|
| 14.0.3 | 3 / 0 | |
| 14.0.2 | 3 / 0 | |
| 14.0.1 | 3 / 0 | |
| 13.5.9 | 3 / 0 | |
| 13.5.8 | 3 / 0 | |
| 13.5.7 | 3 / 0 | |
| 13.5.6 | 3 / 0 | |
| 13.5.5 | 3 / 0 | |
| 13.5.4 | 3 / 0 | |
| 13.5.3 | 3 / 0 | |
| 13.5.2 | 3 / 0 | |
| 13.5.1 | 3 / 0 | |
| 13.4.4 | 3 / 0 | |
| 13.4.3 | 3 / 0 | |
| 13.4.2 | 3 / 0 | |
| 13.4.1 | 3 / 0 | |
| 13.3.1 | 3 / 0 | |
| 13.2.3 | 3 / 0 | |
| 13.2.2 | 3 / 0 | |
| 13.2.1 | 3 / 0 | |
| 13.1.1 | 3 / 0 | |
| 13.0.2 | 3 / 0 | |
| 13.0.1 | 3 / 0 | |
| 12.6.2 | 3 / 0 | |
| 12.6.1 | 3 / 0 | |
| 12.5.1 | 3 / 0 | |
| 12.4.2 | 3 / 0 | |
| 12.4.1 | 3 / 0 | |
| 12.3.2 | 3 / 0 | |
| 12.3.1 | 3 / 0 | |
| 12.2.2 | 3 / 0 | |
| 12.2.1 | 3 / 0 | |
| 12.1.2 | 3 / 0 | |
| 12.1.1 | 3 / 0 | |
| 12.0.1 | 3 / 0 | |
| 11.1.3 | 3 / 0 | |
| 11.1.2 | 3 / 0 | |
| 11.1.1 | 3 / 0 | |
| 11.0.2 | 3 / 0 | |
| 11.0.1 | 3 / 0 | |
| 10.4.2 | 3 / 0 | |
| 10.4.1 | 3 / 0 | |
| 10.3.1 | 3 / 0 | |
| 10.2.6 | 3 / 0 | |
| 10.2.5 | 3 / 0 | |
| 10.2.4 | 3 / 0 | |
| 10.2.3 | 3 / 0 | |
| 10.2.2 | 3 / 0 | |
| 10.2.1 | 3 / 0 | |
| 10.1.14 | 3 / 0 | |
| 10.1.13 | 3 / 0 | |
| 10.1.12 | 3 / 0 | |
| 10.1.11 | 3 / 0 | |
| 10.1.10 | 3 / 0 | |
| 10.1.9 | 3 / 0 | |
| 10.1.8 | 3 / 0 | |
| 10.1.7 | 3 / 0 | |
| 10.1.6 | 3 / 0 | |
| 10.1.5 | 3 / 0 | |
| 10.1.4 | 3 / 0 | |
| 10.1.3 | 3 / 0 | |
| 10.1.2 | 3 / 0 | |
| 10.1.1 | 3 / 0 | |
| 10.0.2 | 3 / 0 | |
| 10.0.1 | 3 / 0 | |
| 9.7.2 | 3 / 0 | |
| 9.7.1 | 3 / 0 | |
| 9.6.2 | 3 / 0 | |
| 9.6.1 | 3 / 0 | |
| 9.5.1 | 3 / 0 | |
| 9.4.1 | 3 / 0 | |
| 9.3.1 | 3 / 0 | |
| 9.2.1 | 3 / 0 | |
| 9.1.1 | 3 / 0 | |
| 9.0.1 | 3 / 0 | |
| 8.7.1 | 3 / 0 | |
| 8.6.1 | 3 / 0 | |
| 8.5.1 | 3 / 0 | |
| 8.4.1 | 3 / 0 | |
| 8.3.3 | 3 / 0 | |
| 8.3.2 | 3 / 0 | |
| 8.3.1 | 3 / 0 | |
| 8.2.2 | 3 / 0 | |
| 8.1.2 | 3 / 0 | |
| 8.1.1 | 3 / 0 | |
| 8.0.5 | 3 / 0 | |
| 8.0.4 | 3 / 0 | |
| 8.0.3 | 3 / 0 | |
| 8.0.2 | 3 / 0 | |
| 8.0.1 | 3 / 0 | |
| 8.0.0 | 3 / 0 | |
| 7.9.2 | 3 / 0 | |
| 7.9.1 | 3 / 0 | |
| 7.8.2 | 3 / 0 | |
| 7.8.1 | 3 / 0 | |
| 7.7.1 | 3 / 0 | |
| 7.6.1 | 3 / 0 | |
| 7.5.1 | 3 / 0 | |
| 7.4.1 | 3 / 0 | |
| 7.3.1 | 3 / 0 |
v14.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.