← Home

@stripe/extensibility-sdk

npm Repository Homepage

Stripe Apps Extensibility SDK - API objects, standard library, and ESLint rules

8
Versions
MIT
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

nazli-stripestripejsjordand-stripearashn-stripemaxliu-stripejackieosborn-stripebillfinn-stripelins-stripestripe-bindingsjil-stripetomas-stripebibek-striperado-stripefkuo-stripechaves-stripeporter-stripelemuel-stripengrubb-stripecchalstrom-stripecharliecruzan-stripemattpatt-stripeericfrank-stripetomer-stripemindy-stripetennhard-stripejackokerman-stripeianjabour-stripestegs-stripejeremyg-stripeebarrenechea-stripestevekaliski-stripematebek-stripehenryx-stripekovalev-stripetylerkrupickastripeaywang-striperaulfdm-stripecttsai-stripetjc-stripetimbennett-stripebethanychen-striperussill-stripekysley-stripecjmisenas-stripejar-stripevladpotapov-stripedavidme-stripejohno-stripesvenugopal-stripealexander-stripetoluo-stripetillh-stripewooj-stripejoyceqin-stripejaynewstrom-stripegbirch-stripeluisv-stripelamflam-stripetjclawson-stripematv-stripelng-stripemats-stripesamer-stripe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@formspec/core AI (dependencies): Intentional alpha dependency in an official Stripe SDK; stable pattern for this package. ai
provenance publisher-changed AI (provenance): Stripe org migrated publishing to GitHub Actions CI/CD; expected pattern for this package going forward. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers have stripe-suffixed usernames consistent with Stripe org rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of old maintainers alongside addition of stripe-suffixed accounts is consistent with org-level rotation, not takeover. ai
provenance no-provenance AI (provenance): Official Stripe org package; absence of Sigstore provenance is acceptable for this publisher. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.1 1 / 8
0.27.1 1 / 8
0.26.0 1 / 8
0.25.0 1 / 8
0.24.1 1 / 8
0.24.0 1 / 8
0.23.0 1 / 8
0.22.4 1 / 8

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v0.27.1

2 findings
HIGH Publisher changed: jar-stripe → GitHub Actions (on 2026-05-19) provenance

This version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.26.0

2 findings
HIGH Publisher changed: jar-stripe → GitHub Actions (on 2026-05-07) provenance

This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.25.0

2 findings
HIGH Publisher changed: jar-stripe → GitHub Actions (on 2026-05-05) provenance

This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.24.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.

v0.24.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.

v0.22.4

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.