# google/or-tools — health index 91/100 (Excellent)

> Inspection of the public repository google/or-tools by inspect.software. It holds a health index of 91 out of 100, placing it in the Excellent band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/google/or-tools
- Report page: https://inspect.software/software/google/or-tools
- Full JSON report: https://inspect.software/api/repositories/google/or-tools/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/g/google/or-tools.svg
- Inspected: 2026-08-27
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 75/100 | Good |
| Community & Adoption | 17% | 96/100 | Exceptional |
| Sustainability & Governance | 23% | 78/100 | Good |
| Engineering Quality | 19% | 74/100 | Good |
| Security | 16% | 60/100 | Moderate |
| AI Readiness | 4% | 75/100 | Good |

The weighted overall 77 is calibrated to 91 on the published index scale (record calibration 2026-08-02).

## Repository facts

| Field | Value |
|---|---|
| Description | Google's Operations Research tools: |
| Homepage | https://developers.google.com/optimization/ |
| Primary language | C++ |
| License | Apache-2.0 |
| Stars | 13,956 |
| Forks | 2,474 |
| Created | 2015-02-21 |
| Last push | 2026-08-27 |
| Latest release | v9.15 |
| Commits (last year) | 250 |
| Bus factor | 2 |
| Topics | combinatorial-optimization, linear-programming, operations-research, optimization, or-tools |

## Vitality — 75/100 (Good)

Is the project alive — is code being written and are releases shipping? Weight: 21% of the overall index.

### Development activity — 79/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | partial | 17.3 / 36 | 25/52 weeks with commits |
| Commit volume | met | 18 / 18 | 250 commits in the last year |
| OpenSSF Scorecard: Maintained | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Release discipline — 70/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 52 releases published |
| Release recency | partial | 16.2 / 36 | latest release 227 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~115.1 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Abandonment — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 78 days ago |

## Community & Adoption — 96/100 (Exceptional)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 17% of the overall index.

### Popularity & adoption — 99/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | met | 60 / 60 | 13,956 stars |
| Forks | met | 25 / 25 | 2,474 forks |
| Watchers | partial | 13.8 / 15 | 310 watchers |

### Community health — 92/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (Apache-2.0) |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | met | 6.3 / 6.3 | — |

## Sustainability & Governance — 78/100 (Good)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 23% of the overall index.

### Maintainer resilience (bus factor) — 56/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 25.2 / 54 | 2 contributor(s) cover half of all commits |
| Commit distribution | partial | 11.7 / 22.5 | top contributor authored 48% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 99 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 84/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 40.8 / 42 | 97% of issues closed |
| PR acceptance | partial | 22 / 30 | 636/868 decided PRs merged |
| Newcomer PR acceptance | partial | 8.7 / 13 | 2/3 first-time contributors' PRs merged in 30d |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

### Ownership & stewardship — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | met | 20 / 20 | — |
| Owner reach | met | 25 / 25 | 77,510 followers of google |
| Track record | met | 25 / 25 | 2897 public repos, account ~14 yr old |

## Engineering Quality — 74/100 (Good)

Are baseline engineering and documentation practices in place? Weight: 19% of the overall index.

### Engineering practices — 80/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 34 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .pylintrc |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 65/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://developers.google.com/optimization/ |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 5 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 60/100 (Moderate)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Security policy (SECURITY.md) | not met | 0 / 30 | — |
| Dependabot config | met | 25 / 25 | — |
| Dependency lockfiles | met | 25 / 25 | go.sum |
| CodeQL workflow | not met | 0 / 20 | — |

### Dependency advisories — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 114 resolved dependencies against OSV; 2 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

### High-Risk Jurisdiction Exposure — 100/100 (Exceptional)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 75/100 (Good)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 33/100 (At Risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | partial | 32.7 / 40 | 60 of 98 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 89/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | met | 18 / 18 | Makefile, bazel/Makefile, cmake/Makefile, makefiles/Makefile, ortools/flatzinc/challenge/Makefile, tools/docker/Makefile |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .pylintrc |
| Static type checking | met | 11 / 11 | C++ (statically typed) |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | met | 8 / 8 | 2 of the last 100 commits are automated dependency updates |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Code legibility for models — 98/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | C++ (statically typed) |
| Manageable file sizes | partial | 53 / 55 | 88/2443 source files over 60KB |

### Machine-readable interfaces — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | met | 40 / 40 | ortools/bop/bop_parameters.proto, ortools/constraint_solver/assignment.proto, ortools/constraint_solver/demon_profiler.proto, ortools/constraint_solver/routing_enums.proto, ortools/constraint_solver/routing_heuristic_parameters.proto, ortools/constraint_solver/routing_ils.proto, ortools/constraint_solver/routing_parameters.proto, ortools/constraint_solver/search_limit.proto, ortools/constraint_solver/search_stats.proto, ortools/constraint_solver/solver_parameters.proto, ortools/glop/parameters.proto, ortools/graph/flow_problem.proto, ortools/linear_solver/linear_solver.proto, ortools/math_opt/callback.proto, ortools/math_opt/cpp/enums_test.proto, ortools/math_opt/infeasible_subsystem.proto, ortools/math_opt/model.proto, ortools/math_opt/model_parameters.proto, ortools/math_opt/model_update.proto, ortools/math_opt/parameters.proto, ortools/math_opt/result.proto, ortools/math_opt/rpc.proto, ortools/math_opt/solution.proto, ortools/math_opt/solvers/glpk.proto, ortools/math_opt/solvers/gscip/gscip.proto, ortools/math_opt/solvers/gurobi.proto, ortools/math_opt/solvers/highs.proto, ortools/math_opt/solvers/osqp.proto, ortools/math_opt/solvers/xpress.proto, ortools/math_opt/sparse_containers.proto, ortools/packing/multiple_dimensions_bin_packing.proto, ortools/packing/vector_bin_packing.proto, ortools/pdlp/solve_log.proto, ortools/pdlp/solvers.proto, ortools/routing/parsers/capacity_planning.proto, ortools/sat/boolean_problem.proto, ortools/sat/cp_model.proto, ortools/sat/cp_model_service.proto, ortools/sat/lrat.proto, ortools/sat/routes_support_graph.proto, ortools/sat/sat_parameters.proto, ortools/scheduling/course_scheduling.proto, ortools/scheduling/jobshop_scheduling.proto, ortools/scheduling/rcpsp.proto, ortools/service/v1/mathopt/model.proto, ortools/service/v1/mathopt/model_parameters.proto, ortools/service/v1/mathopt/parameters.proto, ortools/service/v1/mathopt/result.proto, ortools/service/v1/mathopt/solution.proto, ortools/service/v1/mathopt/solver_resources.proto, ortools/service/v1/mathopt/sparse_containers.proto, ortools/service/v1/optimization.proto, ortools/set_cover/capacity.proto, ortools/set_cover/set_cover.proto, ortools/util/int128.proto, ortools/util/optional_boolean.proto |
| MCP server | excluded | 0 / 20 | not applicable to this kind of software |
| Runnable examples | met | 40 / 40 | examples, notebooks, samples |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Could not fetch go package 'github.com/google/or-tools' from its registry
- OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt