withastro/astro

Prefer this fork if you want Astro with custom i18n, font, middleware, and server-islands work and can tolerate upstream lag. Prefer upstream if you want the safest path, current fixes, and lower maintenance overhead.

Prefer this fork only if you specifically want its older customized snapshot and local workflow additions. If you want a production-ready Astro base or close upstream compatibility, current upstream is the better choice.

Prefer upstream unless you specifically need this exact fork as a starting snapshot; it adds no visible features and is materially behind current Astro maintenance.

Choose this fork if you want a patched Astro branch for stability and specific bug fixes, especially in routing, content, and build behavior. Choose upstream if you want the newest releases and lower maintenance overhead.

Choose this fork only if you need its custom maintenance line and can own the divergence. If you want the current Astro experience, upstream is the safer default.

Prefer this fork only if its added fixes and workflow changes match a specific operational need you own. If you want the safest default Astro experience, upstream is the better baseline because this fork is materially diverged and behind.

Prefer this fork if you want Astro plus custom maintenance/triage automation and you are willing to own a long-term divergence from upstream. Prefer upstream if you need the latest framework fixes, cleaner upgrade paths, and standard Astro tooling.

Choose this fork only if you need its custom behavior and can absorb the maintenance cost. For most adopters, upstream Astro is the safer default; this fork is better for teams explicitly seeking a customized, divergence-heavy codebase and not expecting easy upstream rebases.

Prefer this fork only if its custom automation and local content changes are exactly what you need. For general Astro adoption, upstream is the better default because this fork is stale and materially diverged.