@zthun/bouncer-web
A documentation website for showing bouncer.
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:dist/assets/index-Bh7BydIy.js | AI (source-diff): Standard Vite build output (minified bundle); not obfuscated malware. Stable pattern for this frontend docs package. | ai | |
| source-diff | net-exec-file:dist/assets/index-Bh7BydIy.js | AI (source-diff): Network calls are Vite modulepreload polyfill fetch(); no dynamic code execution beyond normal module loading. | ai | |
| source-diff | net-exec-file:dist/assets/index-Bq0BnaM9.js | AI (source-diff): Vite-bundled SPA asset; fetch+dynamic-module pattern is standard browser modulepreload polyfill, not malware. | ai | |
| source-diff | net-exec-file:dist/assets/index-BvKA1Ynh.js | AI (source-diff): Vite-bundled frontend asset; fetch() is a modulepreload polyfill, not malicious network+exec. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from bundling React and deps into a single Vite dist asset for a documentation site. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.1.3 | 0 / 16 | |
| 4.1.2 | 0 / 16 | |
| 4.1.1 | 0 / 15 | |
| 4.1.0 | 0 / 15 | |
| 4.0.1 | 0 / 3 | |
| 4.0.0 | 0 / 3 |
v4.1.3
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.