@cardano-sdk/core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@cardano-ogmios/client | AI (phantom-deps): Referenced in config files as noted; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cardano-ogmios/schema | AI (phantom-deps): Referenced in config files as noted; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Established IOG Cardano SDK package; name similarity to 'cors' is coincidental and not a typosquat. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Core SDK library in a large monorepo; sparse README is expected for a library package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.46.12 | 13 / 9 | |
| 0.46.11 | 13 / 9 | |
| 0.46.10 | 13 / 9 | |
| 0.46.7 | 13 / 9 | |
| 0.46.3 | 13 / 9 | |
| 0.46.2 | 13 / 9 |
v0.46.12
2 findingsPackage name '@cardano-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.11
2 findingsPackage name '@cardano-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.