@hot-updater/supabase
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 | publisher-changed | AI (provenance): Transition to GitHub Actions publishing with SLSA attestation; legitimate CI/CD migration for this package. | ai | |
| dependencies | unvetted-dep:@hot-updater/core | AI (dependencies): Same-monorepo sibling dep at matching version; stable pattern across all @hot-updater/* releases. | ai | |
| dependencies | unvetted-dep:@hot-updater/cli-tools | AI (dependencies): Same-monorepo sibling dep at matching version; stable pattern across all @hot-updater/* releases. | ai | |
| dependencies | unvetted-dep:@hot-updater/plugin-core | AI (dependencies): Same-monorepo sibling dep at matching version; stable pattern across all @hot-updater/* releases. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is a declared runtime dependency used in edge function build; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:uuidv7 | AI (phantom-deps): uuidv7 is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): All raw IP references are 127.0.0.1 in integration test specs — not production network calls. | ai |
Versions (showing 77 of 177)
| Version | Deps | Published |
|---|---|---|
| 0.20.5 | 3 / 7 | |
| 0.20.4 | 3 / 7 | |
| 0.20.3 | 3 / 7 | |
| 0.20.2 | 3 / 7 | |
| 0.20.1 | 3 / 7 | |
| 0.20.0 | 3 / 7 | |
| 0.19.10 | 3 / 7 | |
| 0.19.9 | 3 / 7 | |
| 0.19.8 | 3 / 7 | |
| 0.19.7 | 3 / 7 | |
| 0.19.6 | 3 / 7 | |
| 0.19.5 | 3 / 7 | |
| 0.19.4 | 3 / 7 | |
| 0.19.3 | 3 / 7 | |
| 0.19.2 | 3 / 7 | |
| 0.19.1 | 3 / 7 | |
| 0.19.0 | 3 / 7 | |
| 0.18.5 | 3 / 7 | |
| 0.18.4 | 3 / 7 | |
| 0.18.3 | 3 / 7 | |
| 0.18.2 | 3 / 7 | |
| 0.18.1 | 3 / 7 | |
| 0.18.0 | 3 / 7 | |
| 0.17.0 | 3 / 7 | |
| 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 | |
| 0.12.7 | 3 / 4 | |
| 0.12.6 | 3 / 4 | |
| 0.12.5 | 3 / 4 | |
| 0.12.4 | 3 / 4 | |
| 0.12.3 | 3 / 4 | |
| 0.12.2 | 3 / 4 | |
| 0.12.1 | 3 / 4 | |
| 0.12.0 | 3 / 4 | |
| 0.11.0 | 3 / 4 | |
| 0.10.2 | 3 / 4 | |
| 0.10.1 | 3 / 4 | |
| 0.10.0 | 3 / 4 | |
| 0.9.0 | 3 / 4 | |
| 0.8.0 | 3 / 4 | |
| 0.7.0 | 3 / 4 | |
| 0.6.7 | 3 / 4 | |
| 0.6.6 | 3 / 4 | |
| 0.6.5 | 3 / 4 | |
| 0.6.4 | 3 / 4 | |
| 0.6.3 | 3 / 4 | |
| 0.6.2 | 3 / 4 | |
| 0.6.1 | 3 / 4 | |
| 0.6.0 | 4 / 3 | |
| 0.5.10 | 4 / 3 | |
| 0.5.9 | 4 / 3 | |
| 0.5.8 | 4 / 3 | |
| 0.5.7 | 4 / 3 | |
| 0.5.6 | 4 / 3 | |
| 0.5.5 | 4 / 3 | |
| 0.5.4 | 4 / 3 | |
| 0.5.3 | 4 / 3 | |
| 0.5.2 | 4 / 3 | |
| 0.5.1 | 4 / 3 | |
| 0.5.0 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.1 | 4 / 3 | |
| 0.3.0 | 4 / 3 |
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.
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.