@metamask/ocap-kernel
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@endo/import-bundle | AI (dependencies): @endo/import-bundle is part of the Agoric/Endo ecosystem, appropriate for this ocap-kernel package. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask org package; provenance absence is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:ses | AI (phantom-deps): ses is a declared runtime dep used via config/polyfill, not a direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:setimmediate | AI (phantom-deps): setimmediate is a declared runtime dep used via config/polyfill; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 36 / 26 | |
| 0.6.0 | 35 / 26 | |
| 0.5.0 | 18 / 26 | |
| 0.4.0 | 18 / 26 | |
| 0.3.0 | 18 / 26 | |
| 0.2.0 | 18 / 26 | |
| 0.1.0 | 18 / 26 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.