@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 38 of 138)
| Version | Deps | Published |
|---|---|---|
| 0.12.7 | 3 / 7 | |
| 0.12.6 | 3 / 7 | |
| 0.12.5 | 2 / 6 | |
| 0.12.4 | 2 / 6 | |
| 0.12.3 | 2 / 6 | |
| 0.12.2 | 2 / 6 | |
| 0.12.1 | 2 / 6 | |
| 0.12.0 | 2 / 6 | |
| 0.11.0 | 2 / 6 | |
| 0.10.2 | 2 / 6 | |
| 0.10.1 | 2 / 6 | |
| 0.10.0 | 2 / 6 | |
| 0.9.0 | 2 / 6 | |
| 0.8.0 | 2 / 6 | |
| 0.7.0 | 2 / 6 | |
| 0.6.7 | 2 / 6 | |
| 0.6.6 | 2 / 6 | |
| 0.6.5 | 2 / 6 | |
| 0.6.4 | 2 / 6 | |
| 0.6.3 | 2 / 6 | |
| 0.6.2 | 2 / 6 | |
| 0.6.1 | 2 / 6 | |
| 0.6.0 | 2 / 6 | |
| 0.5.10 | 2 / 6 | |
| 0.5.9 | 2 / 6 | |
| 0.5.8 | 2 / 6 | |
| 0.5.7 | 2 / 6 | |
| 0.5.6 | 2 / 6 | |
| 0.5.5 | 2 / 6 | |
| 0.5.4 | 2 / 6 | |
| 0.5.3 | 2 / 6 | |
| 0.5.2 | 2 / 6 | |
| 0.5.1 | 2 / 6 | |
| 0.5.0 | 2 / 6 | |
| 0.4.0 | 1 / 7 | |
| 0.3.1 | 1 / 7 | |
| 0.3.0 | 1 / 7 | |
| 0.2.0 | 1 / 7 |
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.