bazelbuild/bazel

a fast, scalable, multi-language and extensible build system

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 2nd, 2026
Created on June 12th, 2014
Open Issues & Pull Requests: 1,852 (+0)
GitHub issues: Enabled
Number of forks: 4,594
Total Stargazers: 25,816 (+1)
Total Subscribers: 598 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 981
New in 7 days: 23
Closed in 7 days: 73
Avg open age: 814 days
Stale 30+ days: 826
Stale 90+ days: 646

Recent activity

Opened in 7 days: 20
Closed in 7 days: 59
Comments in 7 days: 27
Events in 7 days: 91

Top labels

  • type: bug (1,443)
  • type: feature request (859)
  • untriaged (774)
  • P3 (771)
  • P2 (726)
  • team-OSS (551)
  • stale (518)
  • team-ExternalDeps (424)

Detailed Description

Bazel is a build system that compiles code and runs tests for projects spanning multiple programming languages and large codebases.

Bazel addresses the problem of building and testing complex software at scale by using a dependency graph model where each build target declares its inputs and outputs explicitly. The system evaluates only the dependencies needed for a given task, enabling incremental builds and parallel execution. It caches build artifacts and test results, avoiding redundant work across builds and across machines in a distributed setup. Bazel's hermetic build model isolates builds from the host system, making them reproducible and portable across different machines and environments.

Bazel suits large monorepos and projects with multiple languages where build performance and correctness matter. Teams managing codebases with hundreds of thousands of files, or those needing consistent builds across many developers and CI systems, benefit from its caching and reproducibility guarantees. The tool works well when you can express your build as a directed acyclic graph of dependencies. It is less suited to small single-language projects where simpler build tools suffice, or to workflows where build hermeticity conflicts with your requirements.

The project shows sustained development activity with regular commits addressing bug fixes, performance improvements, and feature additions. Work spans core build logic, language-specific rule sets, and the remote execution protocol that enables distributed builds. The maintainers actively respond to issues and pull requests, indicating ongoing engagement with the user community. Development includes refinements to the caching system, improvements to build performance, and expansions of language support through new and updated rules.