← Home

@stripe/stripe-js

npm Repository Homepage
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

rado-stripebmathews-stripecbala-stripedodgez-stripealaycock-stripekdeland-stripebdaily-stripervolyar-stripetjliu-stripealic-stripe

Keywords

StripeStripe.jsElements

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.pattern:stripe AI (typosquat): @stripe/stripe-js is the official Stripe-published package under the @stripe npm scope; the typosquat pattern match is a stable false positive for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require() appears only in test files (src/index.test.ts) as a standard Jest testing pattern; not present in production code. ai

Versions (showing 12 of 12)

Version Deps Published
9.3.1 0 / 25
9.3.0 0 / 25
9.2.0 0 / 25
9.1.0 0 / 25
9.0.1 0 / 25
9.0.0 0 / 25
8.11.0 0 / 25
8.10.0 0 / 25
8.8.0 0 / 25
8.4.0 0 / 24
8.3.0 0 / 24
8.2.0 0 / 24

v9.3.1

2 findings
HIGH typosquat.pattern: Suspicious name similarity to 'stripe' typosquat

Package name '@stripe/stripe-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'stripe'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.