@ocap/mcrypto
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): bn.js is explicitly declared in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped ArcBlock SDK package; not impersonating bcrypt. Levenshtein match is coincidental. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard cryptographic key/hash handling in a blockchain signing library; not obfuscated payload. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.30.24 | 7 / 5 | |
| 1.30.23 | 7 / 5 | |
| 1.30.22 | 7 / 5 | |
| 1.30.21 | 7 / 5 | |
| 1.30.20 | 7 / 5 | |
| 1.30.19 | 7 / 5 | |
| 1.30.18 | 7 / 5 | |
| 1.30.17 | 7 / 5 | |
| 1.30.16 | 7 / 5 | |
| 1.30.15 | 7 / 5 | |
| 1.30.14 | 7 / 5 | |
| 1.30.13 | 7 / 5 | |
| 1.30.12 | 7 / 5 | |
| 1.30.11 | 7 / 5 | |
| 1.30.9 | 7 / 5 | |
| 1.30.7 | 7 / 5 | |
| 1.30.2 | 7 / 5 | |
| 1.30.1 | 7 / 5 | |
| 1.29.27 | 8 / 6 | |
| 1.29.26 | 8 / 6 | |
| 1.29.24 | 8 / 6 | |
| 1.29.23 | 8 / 6 | |
| 1.29.22 | 10 / 7 | |
| 1.29.13 | 10 / 7 | |
| 1.29.7 | 10 / 7 | |
| 1.29.0 | 11 / 7 | |
| 1.28.4 | 11 / 12 | |
| 1.27.16 | 11 / 11 | |
| 1.27.14 | 11 / 11 | |
| 1.27.13 | 11 / 11 | |
| 1.27.12 | 11 / 11 | |
| 1.27.8 | 11 / 11 | |
| 1.27.4 | 11 / 11 | |
| 1.27.3 | 11 / 11 | |
| 1.20.6 | 11 / 11 | |
| 1.20.5 | 11 / 11 |
v1.30.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.