@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 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.