@onesub/shared
Shared types and constants for onesub — server-side receipt validation for react-native-iap
Supply chain provenance
Status for the latest visible version.
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
Keywords
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.7.6 | 0 / 1 | |
| 0.7.5 | 0 / 1 | |
| 0.7.4 | 0 / 1 | |
| 0.7.3 | 0 / 1 | |
| 0.7.2 | 0 / 1 | |
| 0.7.1 | 0 / 1 | |
| 0.7.0 | 0 / 1 | |
| 0.6.0 | 0 / 1 | |
| 0.5.0 | 0 / 1 | |
| 0.4.0 | 0 / 1 | |
| 0.3.5 | 0 / 1 | |
| 0.3.4 | 0 / 1 | |
| 0.3.3 | 0 / 1 | |
| 0.3.2 | 0 / 1 | |
| 0.3.1 | 0 / 1 | |
| 0.3.0 | 0 / 1 | |
| 0.2.1 | 0 / 1 | |
| 0.2.0 | 0 / 1 | |
| 0.1.0 | 0 / 1 |
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
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.