@stripe/terminal-js
Stripe Terminal loading utility
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): Legit transition within Stripe's *-stripe publisher accounts; clean track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Stripe accounts; consistent handoff on scoped official package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires only in test files for parameterized require paths; not present in distributed dist/ code. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 2 / 23 | |
| 0.25.0 | 2 / 23 | |
| 0.24.0 | 2 / 23 | |
| 0.23.0 | 2 / 23 | |
| 0.22.0 | 2 / 23 | |
| 0.21.0 | 2 / 23 | |
| 0.20.0 | 2 / 23 | |
| 0.19.0 | 2 / 23 | |
| 0.18.0 | 2 / 23 | |
| 0.13.0 | 2 / 23 | |
| 0.12.0 | 2 / 23 | |
| 0.11.2 | 2 / 23 | |
| 0.11.0 | 2 / 23 | |
| 0.10.1 | 2 / 23 | |
| 0.10.0 | 2 / 23 | |
| 0.9.1 | 2 / 23 | |
| 0.9.0 | 2 / 23 | |
| 0.8.0 | 0 / 23 | |
| 0.7.0 | 0 / 23 | |
| 0.6.0 | 0 / 23 | |
| 0.5.0 | 0 / 23 | |
| 0.4.0 | 0 / 23 | |
| 0.3.0 | 0 / 23 | |
| 0.2.0 | 0 / 23 | |
| 0.1.1 | 0 / 22 | |
| 0.1.0 | 0 / 22 | |
| 0.0.2 | 0 / 22 |
v0.23.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 (mindy-stripe) than the most recent previously approved version (lins-stripe) on 2025-02-03, but mindy-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.22.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-04. 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.
v0.21.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-04. 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.
v0.20.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-04. 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.
v0.19.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-04. 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.
v0.18.0
2 findingsThis version was published by a different npm account than previous versions on 2024-09-19. 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.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
2 findingsThis version was published by a different npm account (nazli-stripe) than the most recent previously approved version (lins-stripe) on 2023-07-28. It has since remained available on npm for 1093 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.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.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 (lins-stripe) than the most recent previously approved version (jdivock-stripe) on 2022-09-13, but lins-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.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version was published by a different npm account (lins-stripe) than the most recent previously approved version (jdivock-stripe) on 2022-05-04. It has since remained available on npm for 1543 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.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version was published by a different npm account (bibek-stripe) than the most recent previously approved version (jdivock-stripe) on 2021-03-24. It has since remained available on npm for 1949 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.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account (tomas-stripe) than the most recent previously approved version (jdivock-stripe) on 2020-07-13. It has since remained available on npm for 2203 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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.