danielmiessler/Fabric

Prefer this fork only if its added patterns and lightweight serve-mode controls match your needs and you do not need current upstream provider/auth/plugin work. If you want the newest Fabric capabilities or lower maintenance risk, upstream is the better choice.

Prefer this fork only if its custom patterns and narrower scope match your use case. If you need current Fabric integrations, auth, provider support, or active maintenance, upstream is the safer choice.

Choose this fork only if its custom prompt workflows are the goal. For most adopters, upstream Fabric is the safer default because this fork is materially stale and likely missing major recent capabilities.

Choose this fork only if you specifically need an older, stable baseline. For most adopters, upstream Fabric is the better choice because this fork shows no added features and is far behind current development.

Choose this fork only if you want its custom prompt/workflow edits and are comfortable owning a large upstream gap. If you want current Fabric features, provider support, and lower maintenance cost, upstream is the safer choice.

Choose this fork only if you need its early customization layer and are comfortable living far behind upstream. If you want the latest Fabric capabilities, integrations, and maintenance, upstream is the better default.

Choose this fork only if its custom prompt-workflow additions are the point and you are comfortable owning a heavily diverged, stale codebase. If you want current provider support, auth features, and ongoing upstream maintenance, stick with upstream instead.

Prefer upstream unless you specifically need the older snapshot this fork points to. This fork adds no visible capabilities and is materially behind an active upstream, so it is a poor choice for adopters who want current Fabric features or maintenance.

Prefer this fork if you want a customized prompt toolkit and are comfortable maintaining your own branch. Prefer upstream if you want current provider/auth/plugin support and lower maintenance risk.