@stripe/react-connect-js
React components for Connect.js and Connect embedded components
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 | missing-githead | AI (provenance): Manual publish by known Stripe maintainer; benign for this official package. | ai | |
| provenance | no-provenance | AI (provenance): No attestation but official scoped Stripe package; stable FP. | ai | |
| provenance | publisher-changed | AI (provenance): Both publishers are Stripe-org npm accounts; internal rotation, not a takeover signal. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 3.4.3 | 0 / 43 | |
| 3.4.2 | 0 / 43 | |
| 3.4.1 | 0 / 43 | |
| 3.3.36 | 0 / 43 | |
| 3.3.35 | 0 / 43 | |
| 3.3.34 | 0 / 43 | |
| 3.3.33 | 0 / 43 | |
| 3.3.32 | 0 / 43 | |
| 3.3.31 | 0 / 43 | |
| 3.3.30 | 0 / 43 | |
| 3.3.27 | 0 / 43 | |
| 3.3.26 | 0 / 43 | |
| 3.3.25 | 0 / 43 | |
| 3.3.24 | 0 / 43 | |
| 3.3.23 | 0 / 43 | |
| 3.3.22 | 0 / 43 | |
| 3.3.21 | 0 / 40 | |
| 3.3.20 | 0 / 40 | |
| 3.3.19 | 0 / 40 | |
| 3.3.18 | 0 / 40 | |
| 3.3.17 | 0 / 39 | |
| 3.3.16 | 0 / 39 | |
| 3.3.15 | 0 / 39 | |
| 3.3.14 | 0 / 39 | |
| 3.3.13 | 0 / 39 | |
| 3.3.12 | 0 / 39 | |
| 3.3.11 | 0 / 39 | |
| 3.3.10 | 0 / 39 | |
| 3.3.9 | 0 / 39 | |
| 3.3.8 | 0 / 39 | |
| 3.3.7 | 0 / 39 | |
| 3.3.6 | 0 / 39 | |
| 3.3.5 | 0 / 39 | |
| 3.3.4 | 0 / 39 | |
| 3.3.3 | 0 / 39 | |
| 3.3.2 | 0 / 38 | |
| 3.3.1 | 0 / 38 | |
| 3.1.1 | 0 / 38 | |
| 3.0.1 | 0 / 38 | |
| 3.0.0 | 0 / 38 |
v3.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.19
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 (kaiying-stripe) than the most recent previously approved version (dhiggins-stripe) on 2024-11-15, but kaiying-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.3.18
2 findingsPackage 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 2024-10-28. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.17
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 (dhiggins-stripe) than the most recent previously approved version (michaelphines-stripe) on 2024-10-17, but dhiggins-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.3.16
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 (jojo-stripe) than the most recent previously approved version (michaelphines-stripe) on 2024-10-11, but jojo-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.3.15
2 findingsPackage 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 2024-10-04. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.14
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 (hliana-stripe) than the most recent previously approved version (jorgea-stripe) on 2024-09-20, but hliana-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.3.13
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 (bkirk-stripe) on 2024-08-02, 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.3.12
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mxl-stripe.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mxl-stripe) than the most recent previously approved version (bkirk-stripe) on 2024-07-31, but mxl-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.3.11
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 (bkirk-stripe) than the most recent previously approved version (riquelme-stripe) on 2024-07-26, but bkirk-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.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
2 findingsPackage 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 2024-06-27. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
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 (jorgea-stripe) than the most recent previously approved version (jojo-stripe) on 2024-04-17, 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.3.6
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 (jojo-stripe) than the most recent previously approved version (jorgea-stripe) on 2024-04-16, but jojo-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.3.5
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 (jojo-stripe) than the most recent previously approved version (jorgea-stripe) on 2024-04-12, but jojo-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.3.4
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 (jorgea-stripe) than the most recent previously approved version (hliana-stripe) on 2024-04-02, 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.3.3
2 findingsThis version was published by a different npm account (hliana-stripe) than the most recent previously approved version (bkirk-stripe) on 2024-03-06. It has since remained available on npm for 871 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
3 findingsThis version was published by a different npm account (bkirk-stripe) than the most recent previously approved version (kaiying-stripe) on 2024-01-22. It has since remained available on npm for 915 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bkirk-stripe.
v3.3.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 (jorgea-stripe) than the most recent previously approved version (kaiying-stripe) on 2024-01-18, 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.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.
v3.0.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.