@stytch/vanilla-js
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/cjs-dev/shadcn-C7p3HE31.js | AI (source-diff): Minified build output from rollup bundler; code is readable and well-commented, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cjs/shadcn-DnwRqCY0.js | AI (source-diff): Minified build output from rollup bundler; code is readable and well-commented, not obfuscated. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 6.0.9 | 0 / 23 | |
| 6.0.8 | 0 / 23 | |
| 6.0.7 | 0 / 23 | |
| 6.0.6 | 0 / 23 |
v6.0.9
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.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.