Discofork
Repository brief

microsoft/BitNet

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:59:39.981Z
1mo ago

microsoft/BitNet

microsoft/BitNet is the official inference framework for 1-bit LLMs. It is active, widely used, and positioned around fast, lossless CPU and GPU inference for BitNet-style models, with a strong emphasis on optimized kernels and local-device deployment. The repo is current as of 2026-03-10 and has substantial community interest, with 36,875 stars and 3,215 forks.

GitHub
Loading tags...
Stars36,875
Forks3,215
Default branchmain
Last pushed2026-03-10T07:49:47Z
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 you need BitNet on POWER8 or big-endian PowerPC hardware. Stick with upstream if you want the broadest, most current CPU/GPU support and the lowest maintenance risk.

Prefer upstream unless you specifically need the older 2024 snapshot or want a frozen starting point; this fork adds nothing concrete and is behind on important fixes and optimizations.

Prefer upstream unless you specifically need a frozen January 2026 snapshot; this fork adds nothing and lags current BitNet maintenance.

Choose this fork if you want a sovereign local agent platform built around BitNet. Choose upstream if you want the narrower, better-established 1-bit LLM inference stack with less architectural churn.

Choose this fork only if you specifically want a near-upstream mirror; otherwise the official upstream is the better default because this fork shows no added features and is already behind by 3 commits.

Prefer upstream unless you specifically need this older snapshot. For adoption, this fork offers no extra capabilities and carries clear maintenance and recency risk.

Prefer upstream unless you specifically need this exact historical snapshot; this fork adds no evident capabilities and is materially behind current BitNet.

Prefer upstream unless you specifically need this exact snapshot. The fork adds no visible value and is behind on upstream fixes and optimization work.

Prefer upstream unless you specifically need a frozen baseline; this fork adds no visible capabilities and is materially behind on current BitNet improvements.

Do not adopt this fork for active development or deployment. Use upstream instead unless you specifically need the October 2024 snapshot for archival or reproduction purposes.