@stripe/crypto
Stripe Crypto 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): Internal Stripe maintainer rotation, no behavioral change in package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Stripe-internal maintainers added, consistent with official org. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Official Stripe scoped package; name similarity to bcrypt is coincidental, not a typosquat. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require only appears in test files (src/index.test.ts), not in production/dist code. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 0 / 24 | |
| 1.1.1 | 0 / 24 | |
| 1.1.0 | 0 / 24 | |
| 1.0.2 | 0 / 24 | |
| 1.0.1 | 0 / 24 | |
| 1.0.0 | 0 / 24 |
v1.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-17. 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.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. 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.