Good community traction and solid fundamentals. Nearly in the top tier.

The open source control plane for agentic engineering.

Documentation

98

Contributing guide5pt84

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

57

CI/CD14pt0

No CI configuration detected in this repository.

If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt85

Lockfile present (Gemfile.lock). Installs are reproducible.

Tests18pt100

Test files detected (pkg/agents/agent_tools/actions/canvas_test.go).

Linting and formatting5pt100

Formatting enforced (web_src/eslint.config.js).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 326
    Forks
  • 56
    Releaseslatest 5mo ago

Community

  • Community health
  • authors own >50% of commits
  • 3,064
    Watchers

Responsiveness

  • 10h
    Median issue response
  • 4h
    Median PR merge time
  • 514
    Open issues
Repository files45 root entries
  • .agents
  • .bundle
  • .cursor
  • .semaphore
  • .vscode
  • api
  • cmd
  • db
  • docs
  • pkg
    Good: Test files detected (pkg/agents/agent_tools/actions/canvas_test.go).
  • protos
  • rbac
  • release
  • scripts
  • templates
  • test
  • web_src
    Good: Formatting enforced (web_src/eslint.config.js).
  • .air.toml
  • .configuration-fields-baseline.txt
  • .env.example
  • .env.multi-instance.example
  • .gitignore
    Good: .gitignore present.
  • .go-coverage-baseline.json
  • .models-tx-debt-baseline.json
  • .policy.yml
  • AGENTS.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.dev.yml
  • docker-entrypoint.dev.sh
  • docker-entrypoint.sh
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • go.mod
  • go.sum
  • LICENSE
    Good: Licensed under Apache-2.0.
  • lint.toml
  • Makefile
  • NOTICE
  • osv-scanner.toml
  • otel-collector-config.dev.yaml
  • package-lock.json
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • screenshot.png