@stripe/stripe-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 |
|---|---|---|---|---|
| typosquat | typosquat.pattern:stripe | AI (typosquat): @stripe/stripe-js is the official Stripe-published package under the @stripe npm scope; the typosquat pattern match is a stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() appears only in test files (src/index.test.ts) as a standard Jest testing pattern; not present in production code. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.7.0 | 0 / 25 | |
| 9.4.0 | 0 / 25 | |
| 9.3.1 | 0 / 25 | |
| 9.3.0 | 0 / 25 | |
| 9.2.0 | 0 / 25 | |
| 9.1.0 | 0 / 25 | |
| 9.0.1 | 0 / 25 | |
| 9.0.0 | 0 / 25 | |
| 8.11.0 | 0 / 25 | |
| 8.10.0 | 0 / 25 | |
| 8.8.0 | 0 / 25 | |
| 8.4.0 | 0 / 24 | |
| 8.3.0 | 0 / 24 | |
| 8.2.0 | 0 / 24 |
v9.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tjliu-stripe) than the most recent previously approved version (alic-stripe) on 2026-05-26, but tjliu-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.
v9.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
2 findingsPackage name '@stripe/stripe-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'stripe'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.