@metamask/kernel-shims
Ocap Kernel shims
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:ses | AI (phantom-deps): ses is a shim dependency used via bundler/config, not direct import; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@endo/lockdown | AI (phantom-deps): Referenced in bundler config, not direct import; expected for a shim package. | ai | |
| phantom-deps | phantom-dep:@endo/eventual-send | AI (phantom-deps): Referenced in bundler config, not direct import; expected for a shim package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 3 / 26 | |
| 0.4.0 | 3 / 26 | |
| 0.3.0 | 3 / 26 | |
| 0.2.0 | 3 / 26 | |
| 0.1.0 | 3 / 26 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.