Repo brief: google/or-tools

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T20:09:36.652Z · commit 79e340fd50e1

Verdict

Healthy — Strong maintenance signals

• Last commit 2d ago
• 8 active contributors
• Distributed ownership (top contributor 45% of recent commits)
• Apache-2.0 licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Google OR-Tools is an open-source C++ library for solving combinatorial optimization problems at scale, providing constraint programming solvers (CP-SAT, legacy CP), linear programming solvers (Glop simplex, PDLP), and specialized algorithms for TSP/VRP, bin packing, and graph problems. It ships with production-grade Python, Java, C#, and Go bindings via SWIG, enabling developers to use high-performance optimization in their preferred language. Monolithic C++ core (ortools/base, ortools/algorithms, ortools/graph, ortools/linear_solver, ortools/glop, ortools/sat) with SWIG-generated language bindings. Three build systems in parallel: Makefile (legacy), CMake (recommended, ~384KB), and Bazel…

Start here

Open these first:

• BUILD.bazel — Root Bazel build configuration; defines the entire build system and all target dependencies across the project.
• CMakeLists.txt — Root CMake configuration; alternative build system entry point required for cross-platform C++/Java/.NET builds.
• WORKSPACE.bzlmod — Bazel workspace and module definitions; declares all external dependencies and workspace layout.
• MODULE.bazel — Bazel module configuration for dependency management; critical for version pinning and transitive dependency resolution.
• .github/workflows/amd64_linux_bazel.yml — Primary CI/CD pipeline; validates that the core Bazel build and Linux platform work for every commit.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/google/or-tools.git
cd or-tools
# CMake build (recommended for Python/Java/C++):
mkdir build && cd build
cmake -DBUILD_PYTHON=ON -DBUILD_JAVA=ON ..
make -j$(nproc)
# Or use Bazel:
bazel build //ortools/...
# Python wheel install (from PyPI):
pip install ortools

Daily commands:

# Development build with all tests:
bazel test //ortools/... --test_output=errors
# Python samples:
python3 ortools/linear_solver/samples/simple_lp_program.py
# C++ sample:
bazel run //ortools/sat/samples:simple_lp_solver
# Java sample (if built with BUILD_JAVA=ON):
java -cp bazel-bin/ortools/java/com/google/ortools/Loader.jar:... SimpleVrp

…shortened for this brief.

Key cautions & unknowns

• SWIG version sensitivity: Python/Java bindings require specific SWIG versions (check Dockerfile for pinned version); mismatches cause silent runtime failures. Solver licensing: SCIP requires SCIPOptSuite…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.