@cardano-sdk/key-management
Key management types and utilities for Cardano
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:chacha | AI (dependencies): Legitimate ChaCha cipher library used for Cardano key management cryptography. | ai | |
| dependencies | unvetted-dep:@cardano-sdk/dapp-connector | AI (dependencies): Sibling package in the same IOG cardano-js-sdk monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Part of IOG's cardano-js-sdk monorepo with 172 published versions; publisher has 22 approved packages, low takeover risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate SDK sub-package; sparse README/keywords are typical for monorepo component packages. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.29.13 | 13 / 11 | |
| 0.29.12 | 13 / 11 | |
| 0.29.11 | 13 / 11 | |
| 0.29.10 | 13 / 11 | |
| 0.29.9 | 13 / 11 | |
| 0.29.8 | 13 / 11 | |
| 0.29.7 | 13 / 11 | |
| 0.29.6 | 13 / 11 | |
| 0.29.5 | 13 / 11 | |
| 0.29.4 | 13 / 11 | |
| 0.29.3 | 13 / 11 | |
| 0.29.2 | 13 / 11 | |
| 0.29.1 | 13 / 11 | |
| 0.29.0 | 13 / 11 | |
| 0.28.1 | 13 / 11 | |
| 0.28.0 | 13 / 11 | |
| 0.27.11 | 13 / 11 |
v0.29.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.