@hot-updater/standalone
React Native OTA solution for self-hosted
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@hot-updater/core | AI (phantom-deps): Same-org monorepo dep; likely re-exported rather than directly imported. Stable false positive for this package. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 0.20.3 | 2 / 7 | |
| 0.20.2 | 2 / 7 | |
| 0.20.1 | 2 / 7 | |
| 0.20.0 | 2 / 7 | |
| 0.19.10 | 2 / 7 | |
| 0.19.9 | 2 / 7 | |
| 0.19.8 | 2 / 7 | |
| 0.19.7 | 2 / 7 | |
| 0.19.6 | 2 / 7 | |
| 0.19.5 | 2 / 7 | |
| 0.19.4 | 2 / 7 | |
| 0.19.3 | 2 / 7 | |
| 0.19.2 | 2 / 7 | |
| 0.19.1 | 2 / 7 | |
| 0.19.0 | 2 / 7 | |
| 0.18.5 | 2 / 7 | |
| 0.18.4 | 2 / 7 | |
| 0.18.3 | 2 / 7 | |
| 0.18.2 | 2 / 7 | |
| 0.18.1 | 2 / 7 | |
| 0.18.0 | 2 / 7 | |
| 0.17.0 | 2 / 7 | |
| 0.16.6 | 2 / 7 | |
| 0.16.5 | 2 / 7 | |
| 0.16.4 | 2 / 7 | |
| 0.16.3 | 2 / 7 | |
| 0.16.2 | 2 / 7 | |
| 0.16.1 | 2 / 7 | |
| 0.16.0 | 2 / 7 | |
| 0.15.1 | 2 / 7 | |
| 0.15.0 | 2 / 7 | |
| 0.14.0 | 2 / 7 | |
| 0.13.5 | 2 / 7 | |
| 0.13.4 | 2 / 7 | |
| 0.13.3 | 2 / 7 | |
| 0.13.2 | 2 / 7 | |
| 0.13.1 | 2 / 7 | |
| 0.13.0 | 2 / 7 | |
| 0.12.7 | 2 / 7 | |
| 0.12.6 | 2 / 7 | |
| 0.12.5 | 2 / 7 | |
| 0.12.4 | 2 / 5 | |
| 0.12.3 | 2 / 5 | |
| 0.12.2 | 2 / 5 | |
| 0.12.1 | 2 / 5 | |
| 0.12.0 | 2 / 5 | |
| 0.11.0 | 2 / 5 | |
| 0.10.2 | 2 / 5 | |
| 0.10.1 | 2 / 5 |
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.
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.