@revenuecat/purchases-js
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 | no-provenance | AI (provenance): RevenueCat publishes via CI bot without Sigstore attestation; consistent across versions. | ai |
Versions (showing 100 of 102)
| Version | Deps | Published |
|---|---|---|
| 1.48.1 | 0 / 52 | |
| 1.48.0 | 0 / 52 | |
| 1.47.3 | 0 / 52 | |
| 1.47.2 | 0 / 52 | |
| 1.47.1 | 0 / 52 | |
| 1.47.0 | 0 / 52 | |
| 1.46.0 | 0 / 52 | |
| 1.45.0 | 0 / 52 | |
| 1.44.0 | 0 / 52 | |
| 1.43.1 | 0 / 52 | |
| 1.43.0 | 0 / 52 | |
| 1.42.4 | 0 / 52 | |
| 1.42.3 | 0 / 52 | |
| 1.42.2 | 0 / 52 | |
| 1.42.1 | 0 / 52 | |
| 1.42.0 | 0 / 52 | |
| 1.41.2 | 0 / 52 | |
| 1.41.1 | 0 / 52 | |
| 1.41.0 | 0 / 52 | |
| 1.40.0 | 0 / 52 | |
| 1.39.1 | 0 / 52 | |
| 1.39.0 | 0 / 52 | |
| 1.38.0 | 0 / 52 | |
| 1.37.0 | 0 / 52 | |
| 1.36.0 | 0 / 52 | |
| 1.35.1 | 0 / 52 | |
| 1.35.0 | 0 / 52 | |
| 1.34.0 | 0 / 52 | |
| 1.33.0 | 0 / 52 | |
| 1.32.0 | 0 / 52 | |
| 1.30.1 | 0 / 52 | |
| 1.30.0 | 0 / 52 | |
| 1.29.1 | 0 / 52 | |
| 1.29.0 | 0 / 52 | |
| 1.28.0 | 0 / 52 | |
| 1.27.0 | 0 / 52 | |
| 1.26.4 | 0 / 52 | |
| 1.26.3 | 0 / 52 | |
| 1.26.2 | 0 / 52 | |
| 1.26.1 | 0 / 52 | |
| 1.26.0 | 0 / 52 | |
| 1.25.1 | 0 / 52 | |
| 1.25.0 | 0 / 52 | |
| 1.24.4 | 0 / 50 | |
| 1.24.3 | 0 / 50 | |
| 1.24.2 | 0 / 50 | |
| 1.24.1 | 0 / 50 | |
| 1.24.0 | 0 / 50 | |
| 1.23.1 | 0 / 50 | |
| 1.23.0 | 0 / 50 | |
| 1.22.1 | 0 / 50 | |
| 1.22.0 | 0 / 50 | |
| 1.21.1 | 0 / 50 | |
| 1.21.0 | 0 / 50 | |
| 1.20.1 | 0 / 50 | |
| 1.20.0 | 0 / 50 | |
| 1.19.0 | 0 / 50 | |
| 1.18.4 | 0 / 49 | |
| 1.18.3 | 0 / 49 | |
| 1.18.2 | 0 / 49 | |
| 1.18.1 | 0 / 49 | |
| 1.18.0 | 0 / 49 | |
| 1.17.1 | 0 / 49 | |
| 1.17.0 | 0 / 49 | |
| 1.16.1 | 0 / 49 | |
| 1.16.0 | 0 / 49 | |
| 1.15.0 | 0 / 49 | |
| 1.14.3 | 0 / 49 | |
| 1.14.2 | 0 / 49 | |
| 1.14.1 | 0 / 49 | |
| 1.14.0 | 0 / 49 | |
| 1.13.2 | 0 / 49 | |
| 1.13.1 | 0 / 49 | |
| 1.13.0 | 0 / 49 | |
| 1.12.1 | 0 / 49 | |
| 1.12.0 | 0 / 49 | |
| 1.11.1 | 0 / 49 | |
| 1.11.0 | 0 / 49 | |
| 1.10.0 | 0 / 49 | |
| 1.9.0 | 0 / 49 | |
| 1.8.0 | 0 / 49 | |
| 1.7.0 | 0 / 49 | |
| 1.6.0 | 0 / 49 | |
| 1.5.3 | 0 / 49 | |
| 1.5.2 | 0 / 49 | |
| 1.5.1 | 0 / 49 | |
| 1.5.0 | 0 / 49 | |
| 1.4.3 | 0 / 49 | |
| 1.4.2 | 0 / 49 | |
| 1.4.1 | 0 / 49 | |
| 1.4.0 | 0 / 49 | |
| 1.3.0 | 0 / 49 | |
| 1.2.1 | 0 / 49 | |
| 1.2.0 | 0 / 49 | |
| 1.1.0 | 0 / 49 | |
| 1.0.6 | 0 / 49 | |
| 1.0.5 | 0 / 49 | |
| 1.0.4 | 0 / 47 | |
| 1.0.3 | 0 / 47 | |
| 1.0.2 | 0 / 47 |
v1.48.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.