@hot-updater/js
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:qs | AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'qs'. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'jest'. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'rxjs'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'joi'. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'ajv'. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 1 / 5 | |
| 0.31.4 | 1 / 5 | |
| 0.31.3 | 1 / 5 | |
| 0.31.2 | 1 / 5 | |
| 0.31.1 | 1 / 5 | |
| 0.31.0 | 1 / 5 | |
| 0.30.12 | 1 / 5 | |
| 0.30.11 | 1 / 5 | |
| 0.30.10 | 1 / 5 | |
| 0.30.9 | 1 / 5 | |
| 0.30.8 | 1 / 5 | |
| 0.30.7 | 1 / 5 | |
| 0.30.6 | 1 / 5 | |
| 0.30.5 | 1 / 5 | |
| 0.30.4 | 1 / 5 | |
| 0.30.3 | 1 / 5 | |
| 0.30.2 | 1 / 5 | |
| 0.30.1 | 1 / 5 | |
| 0.30.0 | 1 / 5 | |
| 0.29.8 | 1 / 5 | |
| 0.29.7 | 1 / 5 | |
| 0.29.6 | 1 / 5 | |
| 0.29.5 | 1 / 5 | |
| 0.29.4 | 1 / 5 | |
| 0.29.3 | 1 / 5 | |
| 0.29.2 | 1 / 5 | |
| 0.29.1 | 1 / 5 | |
| 0.29.0 | 1 / 5 | |
| 0.28.0 | 1 / 5 | |
| 0.27.1 | 1 / 5 | |
| 0.27.0 | 1 / 5 | |
| 0.26.2 | 1 / 5 | |
| 0.26.1 | 1 / 5 | |
| 0.26.0 | 1 / 5 | |
| 0.25.14 | 1 / 5 | |
| 0.25.13 | 1 / 5 | |
| 0.25.11 | 1 / 5 | |
| 0.25.10 | 1 / 5 | |
| 0.25.9 | 1 / 5 | |
| 0.25.8 | 1 / 5 | |
| 0.25.7 | 1 / 5 | |
| 0.25.6 | 1 / 5 | |
| 0.25.5 | 1 / 5 | |
| 0.25.4 | 1 / 5 | |
| 0.25.3 | 1 / 5 | |
| 0.25.2 | 1 / 5 | |
| 0.25.1 | 1 / 5 | |
| 0.25.0 | 1 / 5 | |
| 0.24.7 | 1 / 5 | |
| 0.24.6 | 1 / 5 | |
| 0.24.5 | 1 / 5 | |
| 0.24.4 | 1 / 5 | |
| 0.24.3 | 1 / 5 | |
| 0.24.2 | 1 / 5 | |
| 0.24.1 | 1 / 5 | |
| 0.24.0 | 1 / 5 | |
| 0.23.1 | 1 / 5 | |
| 0.23.0 | 1 / 5 | |
| 0.22.2 | 1 / 5 | |
| 0.22.1 | 1 / 5 | |
| 0.21.10 | 1 / 5 | |
| 0.21.9 | 1 / 5 | |
| 0.21.8 | 1 / 5 | |
| 0.21.7 | 1 / 5 | |
| 0.21.6 | 1 / 5 | |
| 0.21.5 | 1 / 5 | |
| 0.21.4 | 1 / 5 | |
| 0.21.3 | 1 / 5 | |
| 0.21.2 | 1 / 5 | |
| 0.21.1 | 1 / 5 | |
| 0.21.0 | 1 / 5 | |
| 0.20.15 | 1 / 4 | |
| 0.20.14 | 1 / 4 | |
| 0.20.13 | 1 / 4 | |
| 0.20.12 | 1 / 4 | |
| 0.20.11 | 1 / 4 | |
| 0.20.10 | 1 / 4 | |
| 0.20.9 | 1 / 4 | |
| 0.20.8 | 1 / 4 | |
| 0.20.7 | 1 / 4 | |
| 0.20.6 | 1 / 4 | |
| 0.20.5 | 1 / 4 | |
| 0.20.4 | 1 / 4 | |
| 0.20.3 | 1 / 4 | |
| 0.20.2 | 1 / 4 | |
| 0.20.1 | 1 / 4 | |
| 0.20.0 | 1 / 4 | |
| 0.19.10 | 1 / 4 | |
| 0.19.9 | 1 / 4 | |
| 0.19.8 | 1 / 4 | |
| 0.19.7 | 1 / 4 | |
| 0.19.6 | 1 / 4 | |
| 0.19.5 | 1 / 4 | |
| 0.19.4 | 1 / 4 | |
| 0.19.3 | 1 / 4 | |
| 0.19.2 | 1 / 4 | |
| 0.19.1 | 1 / 4 | |
| 0.19.0 | 1 / 4 | |
| 0.18.5 | 1 / 4 | |
| 0.18.4 | 1 / 4 |
v0.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.5
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.2
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.1
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.7
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.6
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.5
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.2
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.1
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.1
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.11
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.8
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.7
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.6
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.4
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.2
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.1
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.6
2 findingsPackage name '@hot-updater/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.