Discofork
Repository brief

bigskysoftware/htmx

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:36:06.429Z
3mo ago

bigskysoftware/htmx

htmx is a widely used Node.js/JavaScript library for adding AJAX, CSS transitions, WebSockets, and Server-Sent Events directly in HTML through attributes. It is active, not archived, and appears maintained with recent commits and a current pushed date of 2026-03-27.

GitHub
Loading tags...
Stars47,720
Forks1,579
Default branchmaster
Last pushed2026-03-27T10:12:14Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if your target runtime is CitizenFX and you want htmx adapted to that ecosystem. Prefer upstream if you need the broadest compatibility, freshest mainline fixes, or a standard web-app deployment path.

Prefer upstream htmx unless you explicitly want this fork’s source formatting or a personal sandbox. It does not show meaningful functional expansion, and its 530-commit lag makes it a higher-risk adoption than upstream.

Choose this fork only if you want a frozen, self-contained experimental snapshot. If you need current htmx behavior, active maintenance, or easy upstream compatibility, upstream is the better choice.

Choose this fork if you specifically need its custom form-inclusion or error-routing behavior and are comfortable carrying a stale fork. If you want the safest long-term path, upstream htmx is better maintained and likely a better default.

Choose this fork only if you specifically want the extra demo/documentation direction and can tolerate an old, divergent codebase. For normal adoption, upstream is the safer choice.

Choose this fork only if you specifically need an older, frozen htmx snapshot with extra docs/test packaging or legacy compatibility work. For most adopters, upstream is the better default because this fork is stale and materially behind.

Choose upstream unless you specifically need this exact older snapshot; the fork adds no visible capabilities and is materially behind current htmx.

Prefer upstream unless you specifically need an old frozen snapshot; this fork adds no visible value and is far behind current htmx.

Prefer upstream unless you specifically need this exact old snapshot; this fork adds no functionality and is materially stale.

Prefer this fork only if you specifically want its experimental/demo-oriented direction. For normal htmx adoption, upstream is the safer and more current choice.