← Home

@stripe/stripe-identity-react-native

npm Repository Homepage

Stripe identity react native SDK library

11
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-stripetimbennett-stripebethanychen-striperussill-stripekysley-stripecjmisenas-stripejar-stripevladpotapov-stripedavidme-stripesvenugopal-stripealexander-stripetoluo-stripetillh-stripewooj-stripejoyceqin-stripejaynewstrom-stripegbirch-stripeluisv-stripelamflam-stripetjclawson-stripematv-stripelng-stripemats-stripesamer-stripeasmart-stripe

Keywords

react-nativeiosandroid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Stripe org rotates publishing accounts internally; all publishers carry -stripe suffix with clean track records. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers all have stripe-suffixed usernames; consistent with internal Stripe team rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers replaced by stripe-suffixed accounts; no takeover indicators. ai
publish-pattern dormant-publish AI (publish-pattern): Official Stripe SDK; dormancy followed by version bump with no code changes is consistent with periodic maintenance releases. ai

Versions (showing 11 of 11)

Version Deps Published
0.8.0 0 / 20
0.7.0 0 / 20
0.6.0 0 / 20
0.4.1 0 / 20
0.4.0 0 / 20
0.3.8 0 / 20
0.3.7 0 / 20
0.3.6 0 / 20
0.3.5 0 / 20
0.3.4 0 / 20
0.3.3 0 / 20

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.6.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.4.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.4.0

2 findings
HIGH Publisher changed: kentwilliams-stripe → luisv-stripe (on 2025-10-24) provenance

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

LOW No provenance attestation provenance

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

v0.3.8

2 findings
HIGH Publisher changed: kentwilliams-stripe → aywang-stripe (on 2025-06-17) provenance

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

LOW No provenance attestation provenance

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

v0.3.7

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

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.3.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.

v0.3.3

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.