opfs-worker
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/helpers-04x7UBul.cjs | AI (source-diff): Standard Vite minified CJS build output; content is readable OPFS library code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/helpers-ppMRzIAJ.cjs | AI (source-diff): Identical pattern to sibling file — Vite minified CJS bundle, content is benign OPFS library code. | ai | |
| source-diff | obfuscated-file:dist/helpers-CF7A2WQG.cjs | AI (source-diff): Vite-minified build output with source maps; content is clearly OPFS filesystem error classes, not malicious. | ai | |
| source-diff | obfuscated-file:dist/helpers-TAynP0fb.cjs | AI (source-diff): Standard Vite minified build output; sample shows OPFS error classes, not obfuscated malicious code. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is a declared runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 2 / 16 | |
| 1.3.1 | 2 / 16 | |
| 1.3.0 | 2 / 16 | |
| 1.2.4 | 2 / 16 | |
| 1.2.3 | 2 / 16 | |
| 1.2.2 | 2 / 16 | |
| 1.2.1 | 2 / 16 | |
| 1.2.0 | 2 / 16 | |
| 1.1.0 | 2 / 16 | |
| 1.0.1 | 2 / 16 | |
| 1.0.0 | 2 / 16 |
v1.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.
v1.2.4
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.
v1.2.3
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.
v1.2.2
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.
v1.2.1
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.
v1.2.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.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.