@stripe/connect-js
Connect.js loading utility package
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Stripe internal maintainer handoff, stable 971d on npm; not takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate stripe-org maintainer addition. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual to GitHub Actions CI/CD; SLSA attestation confirms legitimate automated publishing. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 3.4.6 | 0 / 29 | |
| 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.31 | 0 / 29 | |
| 3.3.30 | 0 / 29 | |
| 3.3.29 | 0 / 29 | |
| 3.3.28 | 0 / 29 | |
| 3.3.27 | 0 / 29 | |
| 3.3.26 | 0 / 29 | |
| 3.3.25 | 0 / 29 | |
| 3.3.24 | 0 / 29 | |
| 3.3.23 | 0 / 29 | |
| 3.3.22 | 0 / 29 | |
| 3.3.21 | 0 / 26 | |
| 3.3.20 | 0 / 26 | |
| 3.3.19 | 0 / 26 | |
| 3.3.18 | 0 / 26 | |
| 3.3.17 | 0 / 26 | |
| 3.3.16 | 0 / 26 | |
| 3.3.15 | 0 / 26 | |
| 3.3.14 | 0 / 26 | |
| 3.3.13 | 0 / 26 | |
| 3.3.12 | 0 / 26 | |
| 3.3.11 | 0 / 26 | |
| 3.3.10 | 0 / 26 | |
| 3.3.9 | 0 / 26 | |
| 3.3.8 | 0 / 26 | |
| 3.3.7 | 0 / 26 | |
| 3.3.6 | 0 / 26 | |
| 3.3.5 | 0 / 26 | |
| 3.3.4 | 0 / 26 | |
| 3.3.3 | 0 / 26 | |
| 3.3.1 | 0 / 26 | |
| 3.3.0 | 1 / 25 | |
| 3.2.0 | 1 / 25 | |
| 3.1.0 | 1 / 25 | |
| 3.0.1 | 1 / 25 | |
| 3.0.0 | 1 / 25 |
v3.3.22
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 (kaiying-stripe) on 2025-04-22, 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.21
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 (kaiying-stripe) on 2025-02-11, 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.20
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 (michaelphines-stripe) on 2025-01-03, 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.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 (hliana-stripe) than the most recent previously approved version (michaelphines-stripe) on 2024-12-17, 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.18
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 (michaelphines-stripe) than the most recent previously approved version (kaiying-stripe) on 2024-11-19, but michaelphines-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.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 (kaiying-stripe) than the most recent previously approved version (dhiggins-stripe) on 2024-11-13, 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.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 (dhiggins-stripe) than the most recent previously approved version (jojo-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.15
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.14
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.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 (hliana-stripe) than the most recent previously approved version (bkirk-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.12
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 (mxl-stripe) than the most recent previously approved version (bkirk-stripe) on 2024-07-30, 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 (kaiying-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
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 (riquelme-stripe) on 2024-07-11, 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.9
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 (riquelme-stripe) than the most recent previously approved version (kaiying-stripe) on 2024-07-06, but riquelme-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.8
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 (riquelme-stripe) on 2024-07-02, 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.7
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-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.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 (jojo-stripe) than the most recent previously approved version (hliana-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.3
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 (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.1
2 findingsThis version was published by a different npm account (hliana-stripe) than the most recent previously approved version (kaiying-stripe) on 2024-03-05. It has since remained available on npm for 866 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.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 (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.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
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: slye-stripe.
This version was published by a different npm account (slye-stripe) than the most recent previously approved version (kaiying-stripe) on 2023-11-21. It has since remained available on npm for 971 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.