logo

usebruno/bruno

Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)

View on GitHub ↗Jump to charts ↓Open shareable report →

usebruno/bruno has 47k+ stars and 3k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:ApplicationCategory(s):API Development ToolsTesting, QA & Browser AutomationDeveloper Tools
Added to GitGenius on August 31st, 2026
Created on September 27th, 2022
Open Issues & Pull Requests: 1,899 (+2)
GitHub issues: Enabled
Number of forks: 3,011
Total Stargazers: 47,718 (+0)
Total Subscribers: 119 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.6 hours
Mean response time: 58.6 days
90th percentile: 201.3 days
Tracked items: 3,369

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

27 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 12% of issues opened in the past year have never received a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 16 hours, while "mid-term-goal" waits about 4 weeks. 55% of tracked open issues have had no activity in three months. Only 50% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,343
New in 7 days: 19
Closed in 7 days: 13
Avg open age: 416 days
Stale 30+ days: 1,173
Stale 90+ days: 913

Recent activity

Opened in 7 days: 16
Closed in 7 days: 6
Comments in 7 days: 7
Events in 7 days: 42

Top labels

  • bug (1,884)
  • enhancement (1,293)
  • short-term-goal (287)
  • module-qol (167)
  • mid-term-goal (157)
  • has-pr (131)
  • module-request (123)
  • triage-pending (106)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Bruno is an open-source IDE for exploring and testing APIs that serves as a lightweight alternative to Postman and Insomnia.

The tool addresses the need for a privacy-focused, version-control-friendly API client by storing collections directly in the filesystem using a plain text markup language called Bru. This approach enables teams to collaborate on API collections using Git or any version control system, treating API requests as code that can be tracked and reviewed like any other project artifact. Bruno operates entirely offline with no cloud synchronization, keeping all data on the user's device.

Bruno suits teams and developers who prioritize data privacy, want to version-control their API collections alongside their codebase, and prefer not to rely on cloud-based services. It works across Mac, Windows, and Linux, and is available through multiple package managers including Homebrew, Chocolatey, Scoop, Snap, Flatpak, and Apt. The project offers a command-line interface for running collections in automated testing and CI/CD pipelines, making it practical for integration into development workflows beyond interactive API exploration.

The project maintains active development with regular updates across its codebase. The tool has been presented at conferences, indicating ongoing community engagement and visibility. The maintainers have published a long-term vision document outlining their commitment to open-source principles and offline-first design, while offering commercial versions with additional features for teams seeking extended functionality.