@stripe/stripe-identity-react-native
Stripe identity react native SDK library
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): 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 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 0 / 20 | |
| 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 | |
| 0.3.2 | 0 / 20 | |
| 0.3.1 | 0 / 20 | |
| 0.3.0 | 0 / 20 | |
| 0.2.18 | 0 / 20 | |
| 0.2.17 | 0 / 20 | |
| 0.2.16 | 0 / 20 | |
| 0.2.14 | 0 / 20 | |
| 0.2.13 | 0 / 20 | |
| 0.2.12 | 0 / 20 | |
| 0.2.11 | 0 / 20 | |
| 0.2.10 | 0 / 20 | |
| 0.2.9 | 0 / 20 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage 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.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-06-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.