@zthun/pokedex-web
A pokedex in the cloud
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 | net-exec-file:dist/assets/index-BVo5nGRb.js | AI (source-diff): Network calls (fetch for modulepreload) and dynamic patterns are normal Vite bundle output, not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/assets/index-BVo5nGRb.js | AI (source-diff): Standard Vite-bundled frontend output; minification is expected for this web app package. | ai | |
| source-diff | net-exec-file:dist/assets/index-DdhjVzrl.js | AI (source-diff): Vite-bundled SPA output; fetch calls are modulepreload polyfill, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-CLfpQtyP.js | AI (source-diff): Vite-bundled browser app; fetch calls are modulepreload polyfill, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-B3MNxQyN.js | AI (source-diff): Vite-bundled frontend SPA asset; network calls are fetch() for modulepreload polyfill, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-D94-9Kta.js | AI (source-diff): Vite-bundled SPA frontend asset; fetch calls are modulepreload polyfill, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-BMk2xf1q.js | AI (source-diff): File is a standard Vite-bundled SPA asset; network calls are fetch() for modulepreload, not exfiltration or dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-DKnwWWbS.js | AI (source-diff): Vite-bundled browser SPA; fetch calls are modulepreload polyfill, not dropper behavior. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 0 / 24 | |
| 2.1.0 | 0 / 24 | |
| 2.0.11 | 0 / 23 | |
| 2.0.10 | 0 / 23 | |
| 2.0.9 | 0 / 23 | |
| 2.0.8 | 0 / 24 | |
| 2.0.7 | 0 / 24 | |
| 2.0.6 | 0 / 24 | |
| 2.0.5 | 0 / 24 | |
| 2.0.4 | 0 / 24 | |
| 2.0.3 | 0 / 24 | |
| 2.0.2 | 0 / 24 | |
| 2.0.1 | 0 / 24 | |
| 2.0.0 | 2 / 22 |
v2.1.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 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.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
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.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
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.
v2.0.6
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.
v2.0.5
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.
v2.0.4
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.
v2.0.3
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.
v2.0.2
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.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.