@hot-updater/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @hot-updater/core is unrelated to cors; name reflects its role as core module of the hot-updater project. | ai |
Versions (showing 11 of 114)
| Version | Deps | Published |
|---|---|---|
| 0.19.3 | 0 / 1 | |
| 0.19.2 | 0 / 1 | |
| 0.19.1 | 0 / 1 | |
| 0.19.0 | 0 / 1 | |
| 0.18.5 | 0 / 1 | |
| 0.18.4 | 0 / 1 | |
| 0.18.3 | 0 / 1 | |
| 0.18.2 | 0 / 1 | |
| 0.18.1 | 0 / 1 | |
| 0.18.0 | 0 / 1 | |
| 0.17.0 | 0 / 1 |
v0.19.3
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.5
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
2 findingsPackage name '@hot-updater/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.