@hot-updater/js MIT 71 versions

@hot-updater/js

npm Repository Homepage

React Native OTA solution for self-hosted

71

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

gronxb

Keywords

react-nativereact-native-code-pushcode-pusheaseas-updateexpoexpo-updateself-hosted

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	2026/05/14
typosquat	typosquat.levenshtein:jest	AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'jest'.	ai	2026/05/14
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'pg'.	ai	2026/05/14
typosquat	typosquat.levenshtein:rxjs	AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'rxjs'.	ai	2026/05/14
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'joi'.	ai	2026/05/14
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped @hot-updater monorepo package; no impersonation of 'ajv'.	ai	2026/05/14

Versions (showing 71 of 171)

Version	Deps	Published
0.19.9	1 / 4	2025-06-28
0.19.8	1 / 4	2025-06-25
0.19.7	1 / 4	2025-06-23
0.19.6	1 / 4	2025-06-21
0.19.5	1 / 4	2025-06-19
0.19.4	1 / 4	2025-06-16
0.19.3	1 / 4	2025-06-13
0.19.2	1 / 4	2025-06-13
0.19.1	1 / 4	2025-06-12
0.19.0	1 / 4	2025-06-12
0.18.5	1 / 4	2025-06-10
0.18.4	1 / 4	2025-06-09
0.18.3	1 / 4	2025-06-05
0.18.2	1 / 4	2025-06-03
0.18.1	1 / 4	2025-05-30
0.18.0	1 / 4	2025-05-29
0.17.0	1 / 4	2025-04-30
0.16.6	1 / 4	2025-04-27
0.16.5	1 / 4	2025-04-27
0.16.4	1 / 4	2025-04-26
0.16.3	1 / 4	2025-04-17
0.16.2	1 / 4	2025-04-10
0.16.1	1 / 4	2025-04-09
0.16.0	1 / 4	2025-04-07
0.15.1	1 / 4	2025-04-06
0.15.0	1 / 4	2025-04-03
0.14.0	1 / 4	2025-04-01
0.13.5	1 / 4	2025-03-29
0.13.4	1 / 4	2025-03-29
0.13.3	1 / 4	2025-03-28
0.13.2	1 / 4	2025-03-28
0.13.1	1 / 4	2025-03-27
0.13.0	1 / 4	2025-03-26
0.12.7	1 / 3	2025-03-19
0.12.6	1 / 3	2025-03-17
0.12.5	1 / 3	2025-03-17
0.12.4	1 / 3	2025-03-03
0.12.3	1 / 3	2025-02-24
0.12.2	1 / 3	2025-02-23
0.12.1	1 / 3	2025-02-23
0.12.0	1 / 3	2025-02-21
0.11.0	1 / 3	2025-02-20
0.10.2	1 / 3	2025-02-20
0.10.1	1 / 3	2025-02-19
0.10.0	1 / 3	2025-02-19
0.9.0	1 / 3	2025-02-17
0.8.0	1 / 3	2025-02-16
0.7.0	1 / 3	2025-02-14
0.6.7	1 / 3	2025-02-14
0.6.6	1 / 3	2025-02-13
0.6.5	1 / 3	2025-02-05
0.6.4	1 / 3	2025-02-04
0.6.3	1 / 3	2025-02-04
0.6.2	1 / 3	2025-02-02
0.6.1	1 / 3	2025-02-02
0.6.0	1 / 3	2025-01-23
0.5.10	1 / 3	2025-01-22
0.5.9	1 / 3	2025-01-22
0.5.8	1 / 3	2025-01-21
0.5.7	1 / 3	2025-01-21
0.5.6	1 / 3	2025-01-21
0.5.5	1 / 3	2025-01-18
0.5.4	1 / 3	2025-01-18
0.5.3	1 / 3	2025-01-17
0.5.2	1 / 3	2025-01-17
0.5.1	1 / 3	2025-01-17
0.5.0	1 / 3	2025-01-16
0.4.0	1 / 3	2025-01-16
0.3.1	1 / 3	2025-01-16
0.3.0	1 / 3	2025-01-13
0.2.0	1 / 3	2025-01-02

v0.16.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.