/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

danielmiessler/Fabric

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-31T09:44:55.925Z

1mo ago

danielmiessler/Fabric

Fabric is a large, active Go-based open source framework for AI prompt organization and reuse. It is aimed at people who want to integrate AI into existing workflows, with a CLI-centered approach plus docs, a web app, REST API support, and many helper/integration pieces.

Loading tags...

Stars40,278

Forks4,015

Default branchmain

Last pushed2026-03-30T17:16:34Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if its added domain-specific prompts and legacy workflow are the goal. If you want current Fabric features, provider support, or active maintenance, upstream is the better default.

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.

Fork comparison

human-substrate/fabric-legacy

38/100

stale

significant_divergence

Choose this fork only if its added domain-specific prompts and legacy workflow are the goal. If you want current Fabric features, provider support, or active maintenance, upstream is the better default.

Likely purpose

A customized legacy variant for users who want Fabric’s prompt library and CLI workflow, but with extra domain-specific patterns and older operational tooling instead of upstream’s latest provider, auth, and plugin work.

Best for

Users who specifically need the fork’s added prompt patterns and are comfortable staying on an older Fabric base.; Teams maintaining a custom Fabric-like toolchain for specialized content workflows.; Adopters who value stability of a legacy snapshot more than upstream velocity.

Additional features

Adds domain-specific prompt patterns such as legislation analysis, controversy extraction, Alex Hormozi offer, create-graph, recommend_pipeline_upgrades, and recommend_talkpanel_topics.
Includes a Python Streamlit UI path, suggesting a browser-based or lightweight interactive workflow in addition to the upstream CLI-first model.
Contains fork-specific changelog and packaging churn across Python, web, and installer lockfiles, indicating a bundled/customized distribution rather than a clean mirror.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Falls far behind upstream: the fork is 715 commits behind and last pushed on 2024-07-28, while upstream remained active through 2026-03-30.
Likely lacks upstream’s newer provider and auth work, including recent Codex OAuth, Azure AI Gateway, and Azure Entra ID support.
Removes or de-emphasizes upstream material around core helper patterns and content, including files like `sanitize_broken_html_to_markdown`, `suggest_pattern`, and `scripts/python_ui/streamlit.py` changes that suggest older or reshaped workflows.
It trails upstream by 715 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want a frozen, legacy snapshot with custom prompt patterns already added.
May be easier to adapt for niche internal workflows around legislation, offer analysis, and recommendation-style prompts.
The fork’s changes concentrate on user-facing patterns and UI workflow rather than low-level infrastructure rewrites.

Risks

Large divergence from upstream makes future merges costly.
Staleness means missed bug fixes, security updates, provider support, and plugin/auth improvements from upstream.
The fork may be harder to use as a drop-in Fabric replacement because several upstream paths have been removed or heavily rewritten.