@metamask/kernel-browser-runtime
Tools for running the MetaMask Ocap Kernel in a web browser
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/static/sqlite3-opfs-async-proxy-C_otN2ZJ.js | AI (source-diff): Known sqlite-wasm OPFS async proxy worker bundle; minified by design, not malicious. | ai | |
| phantom-deps | phantom-dep:@metamask/kernel-store | AI (phantom-deps): Same-org dep; phantom-dep heuristic fires on indirect usage patterns common in monorepo packages. | ai | |
| phantom-deps | phantom-dep:@metamask/json-rpc-engine | AI (phantom-deps): Same-org dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@metamask/kernel-platforms | AI (phantom-deps): Same-org dep; stable false positive for this monorepo package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 16 / 33 | |
| 0.5.0 | 16 / 33 | |
| 0.4.0 | 15 / 31 | |
| 0.3.0 | 15 / 31 | |
| 0.2.0 | 15 / 32 | |
| 0.1.0 | 15 / 32 |
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.