@stripe/stripe-react-native
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:lib/commonjs/hooks/useCheckout.js | AI (source-diff): Babel-transpiled CommonJS output from react-native-builder-bob; not obfuscated. | ai | |
| source-diff | obfuscated-file:lib/module/hooks/useCheckout.js | AI (source-diff): Babel-transpiled ESM output from react-native-builder-bob; not obfuscated. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): False positive: flagged code is a WebView JS template literal, not an HTTP request to a raw IP. | ai | |
| provenance | no-provenance | AI (provenance): Established Stripe package; lack of Sigstore provenance is acceptable given track record. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.65.0 | 0 / 22 | |
| 0.64.0 | 0 / 21 | |
| 0.63.0 | 0 / 21 | |
| 0.62.0 | 0 / 21 | |
| 0.59.0 | 0 / 21 | |
| 0.57.3 | 0 / 21 | |
| 0.57.2 | 1 / 17 | |
| 0.57.1 | 1 / 17 | |
| 0.57.0 | 0 / 17 | |
| 0.56.0 | 0 / 17 | |
| 0.55.1 | 0 / 17 | |
| 0.55.0 | 0 / 17 | |
| 0.50.3 | 0 / 17 | |
| 0.49.0 | 0 / 17 | |
| 0.47.1 | 0 / 17 | |
| 0.47.0 | 0 / 17 | |
| 0.46.0 | 0 / 17 | |
| 0.45.0 | 0 / 17 | |
| 0.42.1 | 0 / 20 |
v0.65.0
4 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.