@hot-updater/cloudflare MIT 58 versions

@hot-updater/cloudflare

npm Repository Homepage

React Native OTA solution for self-hosted

58

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New deps are official AWS SDK packages; addition is consistent with S3 storage feature expansion.	ai	2026/06/12
dependencies	unvetted-dep:cloudflare	AI (dependencies): cloudflare is the official Cloudflare SDK; expected and stable dependency for this package.	ai	2026/05/30
phantom-deps	phantom-dep:@hot-updater/js	AI (phantom-deps): Same-org monorepo sibling; declared but may be re-exported transitively rather than directly imported.	ai	2026/05/26
phantom-deps	phantom-dep:@hot-updater/core	AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Established monorepo package with 156 versions; sparse README is a style choice, not a spam indicator.	ai	2026/05/14
phantom-deps	phantom-dep:uuidv7	AI (phantom-deps): uuidv7 is declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/14

Versions (showing 58 of 159)

Version	Deps	Published
0.20.1	4 / 17	2025-08-17
0.20.0	4 / 17	2025-08-17
0.19.10	4 / 17	2025-08-16
0.19.9	4 / 17	2025-06-28
0.19.8	4 / 17	2025-06-25
0.19.7	4 / 17	2025-06-23
0.19.6	4 / 17	2025-06-21
0.19.5	4 / 17	2025-06-19
0.19.4	4 / 17	2025-06-16
0.19.3	4 / 17	2025-06-13
0.19.2	4 / 17	2025-06-13
0.19.1	4 / 17	2025-06-12
0.19.0	4 / 17	2025-06-12
0.18.5	4 / 17	2025-06-10
0.18.4	4 / 17	2025-06-09
0.18.3	4 / 17	2025-06-05
0.18.2	4 / 17	2025-06-03
0.18.1	4 / 17	2025-05-30
0.18.0	4 / 17	2025-05-29
0.17.0	4 / 17	2025-04-30
0.16.6	4 / 17	2025-04-27
0.16.5	4 / 17	2025-04-27
0.16.4	4 / 17	2025-04-26
0.16.3	4 / 17	2025-04-17
0.16.2	4 / 17	2025-04-10
0.16.1	4 / 17	2025-04-09
0.16.0	4 / 17	2025-04-07
0.15.1	4 / 17	2025-04-06
0.15.0	4 / 17	2025-04-03
0.14.0	4 / 17	2025-04-01
0.13.5	4 / 17	2025-03-29
0.13.4	4 / 17	2025-03-29
0.13.3	4 / 17	2025-03-28
0.13.2	4 / 17	2025-03-28
0.13.1	4 / 17	2025-03-27
0.13.0	4 / 17	2025-03-26
0.12.7	4 / 15	2025-03-19
0.12.6	4 / 15	2025-03-17
0.12.5	4 / 15	2025-03-17
0.12.4	4 / 15	2025-03-03
0.12.3	4 / 15	2025-02-24
0.12.2	4 / 15	2025-02-23
0.12.1	4 / 15	2025-02-23
0.12.0	4 / 15	2025-02-21
0.11.0	4 / 15	2025-02-20
0.10.2	4 / 15	2025-02-20
0.10.1	4 / 15	2025-02-19
0.10.0	4 / 15	2025-02-19
0.9.0	4 / 15	2025-02-17
0.8.0	4 / 15	2025-02-16
0.7.0	4 / 15	2025-02-14
0.6.7	4 / 15	2025-02-14
0.6.6	4 / 15	2025-02-13
0.6.5	4 / 15	2025-02-05
0.6.4	4 / 15	2025-02-04
0.6.3	4 / 15	2025-02-04
0.6.2	4 / 15	2025-02-02
0.6.1	4 / 15	2025-02-02

v0.19.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.19.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.19.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.19.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.19.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.19.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.19.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.18.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.18.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.17.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.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.