@hot-updater/react-native
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hot-updater/js | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package across all releases. | ai | |
| dependencies | unvetted-dep:@hot-updater/core | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package across all releases. | ai | |
| dependencies | unvetted-dep:@hot-updater/cli-tools | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package across all releases. | ai | |
| dependencies | unvetted-dep:@hot-updater/plugin-core | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package across all releases. | ai | |
| phantom-deps | phantom-dep:@hot-updater/js | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hot-updater/plugin-core | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 100 of 138)
| Version | Deps | Published |
|---|---|---|
| 0.35.7 | 5 / 17 | |
| 0.35.6 | 5 / 17 | |
| 0.35.5 | 5 / 17 | |
| 0.35.4 | 5 / 17 | |
| 0.35.3 | 5 / 12 | |
| 0.35.2 | 5 / 12 | |
| 0.35.1 | 5 / 12 | |
| 0.35.0 | 5 / 12 | |
| 0.34.0 | 5 / 12 | |
| 0.33.2 | 5 / 12 | |
| 0.33.1 | 5 / 12 | |
| 0.33.0 | 5 / 12 | |
| 0.32.0 | 5 / 12 | |
| 0.31.4 | 5 / 12 | |
| 0.31.3 | 5 / 12 | |
| 0.31.2 | 5 / 12 | |
| 0.31.1 | 5 / 12 | |
| 0.31.0 | 5 / 11 | |
| 0.30.12 | 5 / 11 | |
| 0.30.11 | 5 / 11 | |
| 0.30.10 | 5 / 11 | |
| 0.30.9 | 5 / 11 | |
| 0.30.8 | 5 / 11 | |
| 0.30.7 | 5 / 11 | |
| 0.30.6 | 5 / 11 | |
| 0.30.5 | 5 / 11 | |
| 0.30.4 | 5 / 11 | |
| 0.30.3 | 5 / 11 | |
| 0.30.2 | 5 / 11 | |
| 0.30.1 | 5 / 11 | |
| 0.30.0 | 5 / 11 | |
| 0.29.8 | 5 / 11 | |
| 0.29.7 | 5 / 11 | |
| 0.29.6 | 5 / 11 | |
| 0.29.5 | 5 / 11 | |
| 0.29.4 | 5 / 11 | |
| 0.29.3 | 5 / 11 | |
| 0.29.2 | 5 / 11 | |
| 0.29.1 | 5 / 11 | |
| 0.21.10 | 5 / 10 | |
| 0.21.9 | 5 / 10 | |
| 0.21.8 | 5 / 10 | |
| 0.21.7 | 4 / 10 | |
| 0.21.6 | 4 / 10 | |
| 0.21.5 | 4 / 10 | |
| 0.21.4 | 4 / 10 | |
| 0.21.3 | 4 / 10 | |
| 0.21.2 | 4 / 10 | |
| 0.21.1 | 4 / 10 | |
| 0.21.0 | 4 / 10 | |
| 0.20.15 | 4 / 10 | |
| 0.20.14 | 4 / 10 | |
| 0.20.13 | 4 / 10 | |
| 0.20.12 | 4 / 10 | |
| 0.20.11 | 4 / 10 | |
| 0.20.10 | 4 / 10 | |
| 0.20.9 | 4 / 10 | |
| 0.20.8 | 4 / 10 | |
| 0.20.7 | 4 / 10 | |
| 0.20.6 | 4 / 10 | |
| 0.20.5 | 4 / 10 | |
| 0.20.4 | 4 / 10 | |
| 0.20.3 | 4 / 10 | |
| 0.20.2 | 4 / 10 | |
| 0.20.1 | 4 / 10 | |
| 0.20.0 | 4 / 10 | |
| 0.19.10 | 4 / 10 | |
| 0.19.9 | 4 / 10 | |
| 0.19.8 | 3 / 10 | |
| 0.19.7 | 3 / 10 | |
| 0.19.6 | 3 / 10 | |
| 0.19.5 | 3 / 10 | |
| 0.19.4 | 3 / 10 | |
| 0.19.3 | 3 / 10 | |
| 0.19.2 | 3 / 10 | |
| 0.19.1 | 3 / 10 | |
| 0.19.0 | 3 / 10 | |
| 0.18.5 | 3 / 9 | |
| 0.18.4 | 3 / 9 | |
| 0.18.3 | 3 / 9 | |
| 0.18.2 | 3 / 9 | |
| 0.18.1 | 3 / 9 | |
| 0.18.0 | 3 / 9 | |
| 0.17.0 | 3 / 8 | |
| 0.16.6 | 3 / 7 | |
| 0.16.5 | 3 / 7 | |
| 0.16.4 | 3 / 7 | |
| 0.16.3 | 3 / 7 | |
| 0.16.2 | 3 / 7 | |
| 0.16.1 | 3 / 7 | |
| 0.16.0 | 3 / 7 | |
| 0.15.1 | 3 / 7 | |
| 0.15.0 | 3 / 7 | |
| 0.14.0 | 3 / 7 | |
| 0.13.5 | 3 / 7 | |
| 0.13.4 | 3 / 7 | |
| 0.13.3 | 3 / 7 | |
| 0.13.2 | 3 / 7 | |
| 0.13.1 | 3 / 7 | |
| 0.13.0 | 3 / 7 |
v0.35.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.35.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.