@zthun/fashion-web
A react website that demos the fashion components.
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-8fMo3m7s.js | AI (source-diff): Vite-bundled frontend bundle; network calls are browser fetch for modulepreload polyfill, not malicious exfiltration. | ai | |
| source-diff | obfuscated-file:dist/assets/index-h0FrZWhg.js | AI (source-diff): Vite-bundled SPA output; minification is expected for this demo website package. | ai | |
| source-diff | net-exec-file:dist/assets/index-h0FrZWhg.js | AI (source-diff): fetch() calls in modulepreload polyfill + dynamic module loading are standard Vite SPA patterns, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-PeCKW3AX.js | AI (source-diff): Vite-bundled React demo app; fetch calls are modulepreload polyfill, not malicious network execution. | ai | |
| source-diff | net-exec-file:dist/assets/index-DeHSSEuB.js | AI (source-diff): Vite-bundled frontend demo; network calls are modulepreload polyfill fetch, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/assets/index-DTdGNpUL.js | AI (source-diff): Vite-bundled React demo app; fetch calls are modulepreload polyfill, not malicious network execution. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 14.0.2 | 0 / 24 | |
| 14.0.1 | 0 / 24 | |
| 14.0.0 | 0 / 24 | |
| 13.0.5 | 0 / 23 | |
| 13.0.4 | 0 / 23 | |
| 13.0.3 | 0 / 23 | |
| 13.0.2 | 0 / 23 | |
| 13.0.1 | 0 / 22 | |
| 13.0.0 | 0 / 23 |
v14.0.2
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.
v14.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.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.
v13.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.
v13.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.
v13.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.
v13.0.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.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.