@lobb-js/lobb-ext-storage
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): Browser polyfill declared as dep and referenced in Vite config; not directly imported in source is expected for this pattern. | ai | |
| phantom-deps | phantom-dep:browser-fs-access | AI (phantom-deps): Browser API wrapper used via config/indirect reference in a Svelte/Vite build; phantom-dep false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.5.9 | 2 / 16 | |
| 0.5.8 | 2 / 16 | |
| 0.5.7 | 2 / 16 | |
| 0.1.29 | 3 / 15 |
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.