@livestore/devtools-react
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/AllTabs-DXW3FzAR.js | AI (source-diff): Bundled minified output from monorepo build, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/AllTabs-DXW3FzAR.js | AI (source-diff): WASM sqlite + dynamic import in bundled devtools code, no exfil target. | ai | |
| source-diff | obfuscated-file:dist/DevtoolsLazy-mPQl6W7n.js | AI (source-diff): Bundled minified output, same package family. | ai | |
| source-diff | obfuscated-file:dist/index-DUGrlBTh.js | AI (source-diff): Bundled minified output, same package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped sub-package of larger monorepo; metadata sparsity expected. | ai |
v0.2.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.