idb
A small wrapper that makes IndexedDB usable
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/umd-with-async-ittr.js | AI (source-diff): This is a standard rollup+terser minified UMD bundle for the idb library. Long lines are expected minified output, not obfuscation. Stable for this package. | ai | |
| source-diff | obfuscated-file:build/umd.js | AI (source-diff): This is a standard rollup+terser minified UMD bundle for the idb library. Long lines are expected minified output, not obfuscation. Stable for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.0.3 | 0 / 19 | |
| 8.0.0 | 0 / 15 | |
| 7.1.1 | 0 / 15 | |
| 7.0.1 | 0 / 14 | |
| 5.0.6 | 0 / 14 | |
| 4.0.4 | 0 / 16 | |
| 3.0.2 | 0 / 1 |
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.