Discofork
Repository brief

usebruno/bruno

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-30T20:02:57.154Z
1mo ago

usebruno/bruno

Bruno is an open source API client and IDE for exploring and testing APIs, positioned as a lightweight alternative to Postman and Insomnia. It is active, popular, and maintained, with 42,404 stars, 2,254 forks, and recent commits on 2026-03-30.

GitHub
Loading tags...
Stars42,404
Forks2,254
Default branchmain
Last pushed2026-03-30T17:54:11Z
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

Choose this fork if Postman export and collection-search tweaks matter more than staying close to upstream Bruno. Avoid it if you want the latest Bruno fixes, lower merge risk, or the full upstream OpenAPI/sync experience.

Prefer this fork if you want a Bruno-based client tailored to custom API workflows and you can tolerate divergence from upstream. Prefer upstream if you want the broadest feature completeness, safest upgrade path, and the least risk of missing or altered behavior.

Choose this fork only if you want a custom, older Bruno branch with OpenAPI/collection workflow experimentation and you are prepared to maintain it yourself. For most adopters, upstream is the safer choice because this fork is materially stale and likely missing many current fixes and features.

Choose this fork if you want a Bruno-based client with custom theming, tab persistence, and Azure Vault-oriented workflow changes. Choose upstream if you want the newest Bruno fixes and the least maintenance risk.

Choose this fork if you want the extra API-workflow features and can accept upstream lag and higher maintenance risk. Stay on upstream if you want the newest fixes, lower divergence, and easier long-term upgrades.

Choose this fork only if protobuf/proto handling is the main requirement and you are comfortable maintaining a stale, highly diverged codebase. If you want Bruno as a broadly supported API client with current upstream fixes and workflows, upstream is the safer choice.

Choose this fork only if you need its older, customized import/CLI behavior and are willing to maintain it yourself. For most adopters, upstream Bruno is the safer choice because this fork is stale and materially behind.

Choose the upstream project unless you specifically need this exact snapshot for archival or pinning. This fork adds no visible capabilities and is already behind upstream.

Choose upstream unless you specifically need this fork’s ownership or namespace; it adds no visible capabilities and is already slightly behind.

Choose this fork only if you need a nearly pristine copy of Bruno at the current upstream state. For most adopters, upstream is the better default because this fork adds nothing visible and is already behind by one commit.