@hot-updater/bare
React Native OTA solution for self-hosted
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@hot-updater/cli-tools | AI (dependencies): Same-monorepo sibling package, co-released at matching version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@hot-updater/plugin-core | AI (dependencies): Same-monorepo sibling package, co-released at matching version; not an independent risk. | ai |
Versions (showing 11 of 114)
| Version | Deps | Published |
|---|---|---|
| 0.19.3 | 1 / 3 | |
| 0.19.2 | 1 / 3 | |
| 0.19.1 | 1 / 3 | |
| 0.19.0 | 1 / 3 | |
| 0.18.5 | 1 / 3 | |
| 0.18.4 | 1 / 3 | |
| 0.18.3 | 1 / 3 | |
| 0.18.2 | 1 / 3 | |
| 0.18.1 | 1 / 3 | |
| 0.18.0 | 1 / 3 | |
| 0.17.0 | 1 / 3 |
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.