@stytch/react
Stytch's official React Library
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/adminPortal/index.cjs | AI (source-diff): Bundled CJS output with long lines; standard build artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/adminPortal/index.cjs | AI (source-diff): Bundled CJS output with long lines; standard build artifact for this package. | ai | |
| source-diff | net-exec-file:dist/cjs-dev/adminPortal/index.cjs | AI (source-diff): Auth SDK bundle naturally contains network calls and dynamic patterns. | ai | |
| source-diff | net-exec-file:dist/cjs/adminPortal/index.cjs | AI (source-diff): Auth SDK bundle naturally contains network calls and dynamic patterns. | ai | |
| source-diff | obfuscated-file:dist/cjs-dev/shadcn-D6hbC88a.js | AI (source-diff): Bundled CJS output; long lines from build tooling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/shadcn-DL3WnEgS.js | AI (source-diff): Bundled CJS output; long lines from build tooling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/shadcn-B9lEGRrj.js | AI (source-diff): Standard rollup-minified CJS bundle output; readable source comments visible in sample. | ai | |
| source-diff | obfuscated-file:dist/cjs-dev/shadcn-DuV5DMFG.js | AI (source-diff): Standard rollup-minified CJS dev bundle; same pattern as production build. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 20.0.9 | 0 / 16 | |
| 20.0.8 | 0 / 16 | |
| 20.0.6 | 0 / 16 | |
| 19.18.1 | 0 / 20 | |
| 19.18.0 | 0 / 20 | |
| 19.17.0 | 0 / 20 | |
| 19.16.0 | 0 / 20 | |
| 19.15.2 | 0 / 20 | |
| 19.15.1 | 0 / 20 |
v20.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.
v20.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.6
8 findingsThis version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
Newly 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.
Newly 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.
v19.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.