@ocap/util
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped ArcBlock SDK package; Levenshtein match to uuid is coincidental, not impersonation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): fromBase64 is a documented utility function; no obfuscation or payload hiding present. | ai | |
| phantom-deps | phantom-dep:@ocap/types | AI (phantom-deps): Same org scope; likely used for type declarations rather than direct runtime imports. | ai | |
| phantom-deps | phantom-dep:@types/bn.js | AI (phantom-deps): Type-only package; not expected to appear as a direct runtime import. | ai |
Versions (showing 23 of 123)
| Version | Deps | Published |
|---|---|---|
| 1.24.0 | 6 / 11 | |
| 1.23.1 | 6 / 11 | |
| 1.23.0 | 6 / 11 | |
| 1.22.3 | 6 / 11 | |
| 1.22.2 | 6 / 11 | |
| 1.22.1 | 6 / 11 | |
| 1.22.0 | 6 / 11 | |
| 1.21.3 | 5 / 11 | |
| 1.21.2 | 5 / 11 | |
| 1.21.1 | 5 / 11 | |
| 1.21.0 | 5 / 11 | |
| 1.20.16 | 5 / 11 | |
| 1.20.15 | 5 / 11 | |
| 1.20.14 | 5 / 11 | |
| 1.20.13 | 5 / 11 | |
| 1.20.12 | 5 / 11 | |
| 1.20.11 | 5 / 11 | |
| 1.20.10 | 5 / 11 | |
| 1.20.9 | 5 / 11 | |
| 1.20.8 | 5 / 11 | |
| 1.20.7 | 5 / 11 | |
| 1.20.6 | 5 / 11 | |
| 1.20.5 | 5 / 11 |
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.7
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.