alpinejs/alpine

Prefer upstream unless you specifically need a frozen, unmodified snapshot. This fork adds no evident capabilities and is behind by 125 commits, so it is a poor choice for users who want current Alpine fixes and active maintenance.

Prefer upstream unless you need a legacy 2022 snapshot or are continuing an existing fork-specific customization. For new adopters, this fork is too stale and too divergent to be a safe base.

Prefer this fork only if legacy browser support or localized documentation is worth accepting a stale, highly divergent codebase. If you want current Alpine behavior, active fixes, and better long-term maintainability, upstream is the safer choice.

Choose this fork only if legacy browser support or preserving an old Alpine snapshot matters more than staying current. For most adopters, upstream Alpine is the safer choice because this fork is stale and materially behind.

Prefer upstream unless you specifically need an old, frozen Alpine baseline; this fork adds nothing and is behind on multiple bug fixes and improvements.

Prefer upstream unless you specifically need this exact snapshot. This fork adds no visible functionality and is materially behind current Alpine.js, so it is a poor choice for adopters who want active maintenance or the latest fixes.

Prefer upstream unless you specifically need a frozen historical snapshot; this fork adds no visible value and is materially behind current Alpine fixes.

Prefer upstream unless you need this exact historical snapshot. This fork adds no evident features and is materially behind current Alpine.js, so it is a poor choice for ongoing adoption.

Prefer upstream unless you specifically need this exact frozen snapshot. This fork offers no visible advantages over current Alpine.js and lags far behind on fixes and improvements.