@cardano-sdk/crypto
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:i | AI (dependencies): The 'i' package is a well-known pluralization utility; its use here is consistent across versions of this package. | ai | |
| phantom-deps | phantom-dep:npm | AI (phantom-deps): npm listed as dependency is a monorepo tooling artifact; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 40 approved packages under input-output-hk org; dormancy consistent with SDK release cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:ts-log | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Legitimate Cardano SDK crypto package; name reflects SDK namespace, not bcrypt impersonation. | ai | |
| phantom-deps | phantom-dep:ts-custom-error | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:i | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.4.6 | 8 / 12 | |
| 0.4.5 | 8 / 12 | |
| 0.4.4 | 8 / 12 | |
| 0.4.3 | 8 / 12 | |
| 0.4.2 | 9 / 12 | |
| 0.4.1 | 9 / 12 | |
| 0.4.0 | 9 / 12 | |
| 0.3.0 | 9 / 12 | |
| 0.2.3 | 9 / 12 | |
| 0.2.2 | 9 / 12 | |
| 0.2.1 | 9 / 12 | |
| 0.2.0 | 9 / 12 | |
| 0.1.32 | 9 / 12 | |
| 0.1.31 | 9 / 12 | |
| 0.1.30 | 9 / 12 | |
| 0.1.29 | 9 / 12 | |
| 0.1.28 | 9 / 12 | |
| 0.1.27 | 9 / 12 | |
| 0.1.26 | 9 / 12 | |
| 0.1.25 | 9 / 12 | |
| 0.1.24 | 9 / 12 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.