Bubo 🦉
Agentic AI code review with the LLM of your choice. Bubo reviews your GitLab MRs and GitHub PRs with the model you run, and posts only the findings worth acting on as inline threads — no chatbot noise, no praise, no summaries.
- Self-hosted — code, diffs, and review data stay on your infrastructure
- Bring-your-own-LLM — Codex, Claude, or any model your CLI drives
- SCM — Currently supports Gitlab and Github
- findings — Inline or "all good" if clean
- Governance, provenance & an auditable on-prem report - cosign-signed releases with SBOMs
- Metrics — Opentelemetry
Full documentation → mountainowl.github.io/bubo
Install
uv tool install bubo # or: pipx install bubo
bubo init # idempotent; seeds config + workspace + DB
bubo doctor # verify before the first poll
bubo-poller # one poll cycle — dry-run by default, posts nothing
Prefer a container? docker pull ghcr.io/mountainowl/bubo (multi-arch; the
review-agent CLI is BYO). Continue with the
recipes and quickstart.
Documentation
Everything lives on the docs site — this README is just the front door.
| Recipes | Copy-paste GitLab / GitHub / in-house-model setups. |
| Features | The full capability list. |
| Configuration | Every setting, per section, plus a quick-start config. |
| Operate | Deploy, schedule, grade outcomes, governance report. |
| Troubleshooting | Host / infra fixes (sandbox, AppArmor). |
| Metrics & telemetry | Emitted llm_review.* metrics and dashboards. |
Status
- GitLab & GitHub posting via polling — production path, at outcome-metric
parity. Set
[scm].provider = "github"(orBUBO_PROVIDER=github). - MCP server (
bubo-mcp) — read-only metrics + triggered reviews; stdio or HTTP. - Codex or Claude — Bubo runs the review through a wrapper around your agent CLI; Codex ships pre-wired.
- Webhook-driven triggering — not yet; polling is the only path.
Review execution sits outside CI/CD by design — run it as a poller beside your existing pipelines.
Security
config/env.tomlis gitignored and holds tokens. Do not print or commit real values.- Review-agent stdout is redacted (
GITLAB_TOKEN=,OPENAI_API_KEY=,glpat-…,sk-…, credentialed Git URLs) before it touches reports, logs, or the database. - The reviewer subprocess runs under a strict env allowlist — host secrets aren't handed wholesale to the LLM agent.
- Releases are cosign-signed via Sigstore keyless OIDC, with an SBOM on every release.
- Report vulnerabilities per SECURITY.md.
Community
Contributing · Security policy · Support · Code of conduct · License: MIT
Release files for bubo 0.25.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bubo-0.25.3.tar.gz | 415.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bubo-0.25.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:630.2 kB
Release files / bubo-0.25.3.tar.gz
| Download URL | bubo-0.25.3.tar.gz |
|---|---|
| Size | 415.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c11f299beb2f3e6965f8e9d5808abe6585715ad8aebf177310484b35527ea0d7
|
|
BLAKE2b-256 checksum How to use checksums |
06a4c4f3395fd468fccb3a994bca15c5d5ea7cf3acd801e1bbae25e858e5829e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / bubo-0.25.3-py3-none-any.whl
| Download URL | bubo-0.25.3-py3-none-any.whl |
|---|---|
| Size | 215.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed59cb0d1969120c5bf5a3096b6060061f186c5ec736a74d0b96221d897849e6
|
|
BLAKE2b-256 checksum How to use checksums |
3e54ae38a1b140fa94a810b108dfde75522a1a90f58f0ce57417b186def27cd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency log