@metamask/kernel-store
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:@sqlite.org/sqlite-wasm | AI (dependencies): @sqlite.org/sqlite-wasm is the official SQLite WASM package; expected runtime dep for this storage library. | ai | |
| phantom-deps | phantom-dep:ses | AI (phantom-deps): ses is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 4 / 30 | |
| 0.5.0 | 4 / 30 | |
| 0.3.0 | 4 / 29 | |
| 0.2.0 | 4 / 29 | |
| 0.1.0 | 4 / 29 |
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.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.