@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Internal Stripe maintainer handoff (charliecruzan-stripe → davidme-stripe), both org accounts; benign. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Stripe org accounts on official scoped package; legitimate transition. | ai | |
| 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 51 of 93)
| Version | Deps | Published |
|---|---|---|
| 0.71.0 | 0 / 24 | |
| 0.70.0 | 0 / 24 | |
| 0.69.0 | 0 / 24 | |
| 0.68.0 | 0 / 24 | |
| 0.67.0 | 0 / 24 | |
| 0.66.0 | 0 / 24 | |
| 0.65.1 | 0 / 24 | |
| 0.65.0 | 0 / 22 | |
| 0.64.1 | 0 / 24 | |
| 0.64.0 | 0 / 21 | |
| 0.63.0 | 0 / 21 | |
| 0.62.0 | 0 / 21 | |
| 0.61.0 | 0 / 21 | |
| 0.60.0 | 0 / 21 | |
| 0.59.2 | 0 / 21 | |
| 0.59.1 | 0 / 21 | |
| 0.59.0 | 0 / 21 | |
| 0.58.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.54.1 | 0 / 17 | |
| 0.54.0 | 0 / 17 | |
| 0.53.1 | 0 / 17 | |
| 0.53.0 | 0 / 17 | |
| 0.52.0 | 0 / 17 | |
| 0.50.3 | 0 / 17 | |
| 0.50.2 | 0 / 17 | |
| 0.50.1 | 0 / 17 | |
| 0.50.0 | 0 / 17 | |
| 0.49.0 | 0 / 17 | |
| 0.48.0 | 0 / 17 | |
| 0.47.1 | 0 / 17 | |
| 0.47.0 | 0 / 17 | |
| 0.46.0 | 0 / 17 | |
| 0.45.0 | 0 / 17 | |
| 0.44.0 | 0 / 17 | |
| 0.43.0 | 0 / 17 | |
| 0.42.1 | 0 / 20 | |
| 0.42.0 | 0 / 20 | |
| 0.41.0 | 0 / 20 | |
| 0.40.0 | 0 / 20 | |
| 0.39.0 | 0 / 20 | |
| 0.38.6 | 0 / 20 | |
| 0.38.3 | 0 / 20 | |
| 0.38.2 | 0 / 20 | |
| 0.38.1 | 0 / 20 |
v0.71.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mats-stripe) than the most recent previously approved version (cttsai-stripe) on 2026-07-22, but mats-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.70.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cttsai-stripe) than the most recent previously approved version (mats-stripe) on 2026-07-17, but cttsai-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.69.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mats-stripe) than the most recent previously approved version (tjc-stripe) on 2026-07-15, but mats-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidme-stripe) than the most recent previously approved version (jaynewstrom-stripe) on 2026-03-26, but davidme-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.60.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaynewstrom-stripe) than the most recent previously approved version (wooj-stripe) on 2026-03-23, but jaynewstrom-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.59.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mats-stripe) than the most recent previously approved version (samer-stripe) on 2026-03-04, but mats-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.59.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samer-stripe) than the most recent previously approved version (wooj-stripe) on 2026-02-25, but samer-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.58.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wooj-stripe) than the most recent previously approved version (davidme-stripe) on 2026-01-27, but wooj-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.54.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samer-stripe) than the most recent previously approved version (tianzhao-stripe) on 2025-10-02, but samer-stripe is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaynewstrom-stripe) than the most recent previously approved version (tianzhao-stripe) on 2025-09-19, but jaynewstrom-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.53.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-15. This could indicate a legitimate maintainer transition or an account compromise.
v0.52.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gbirch-stripe) than the most recent previously approved version (wooj-stripe) on 2025-09-08, but gbirch-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.50.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gbirch-stripe) than the most recent previously approved version (jaynewstrom-stripe) on 2025-08-06, but gbirch-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.50.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaynewstrom-stripe) than the most recent previously approved version (wooj-stripe) on 2025-07-17, but jaynewstrom-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.48.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (porter-stripe) than the most recent previously approved version (wooj-stripe) on 2025-06-11, but porter-stripe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-20. 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.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.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.