@stripe/connect-js
Connect.js loading utility package
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
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.4.5 | 0 / 29 | |
| 3.4.4 | 0 / 29 | |
| 3.4.3 | 0 / 29 | |
| 3.4.2 | 0 / 29 | |
| 3.4.1 | 0 / 29 | |
| 3.3.39 | 0 / 29 | |
| 3.3.38 | 0 / 29 | |
| 3.3.37 | 0 / 29 | |
| 3.3.36 | 0 / 29 | |
| 3.3.35 | 0 / 29 | |
| 3.3.34 | 0 / 29 | |
| 3.3.33 | 0 / 29 | |
| 3.3.32 | 0 / 29 | |
| 3.3.23 | 0 / 29 |
v3.4.5
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 (jorgea-stripe) than the most recent previously approved version (tomchengcui-stripe) on 2026-05-26, but jorgea-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.
v3.4.4
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 (tomchengcui-stripe) than the most recent previously approved version (carina-stripe) on 2026-05-19, but tomchengcui-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.
v3.4.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-07. 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.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.