agentclientprotocol/registry
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Top 49% of 5,156 graded repos

Registry of agents implementing the Agent Client Protocol (ACP)

Documentation66
Engineering59
Health89
257Apache-2.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (81).

See your top fixes
Now
D
67
Potential
B
81

Top fixes

Highest-impact changes first, ranked by point weight

16 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Expand with a description, install steps, usage, and examples.

  3. 3
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

66

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt60

README is present.

Contributing guide5pt77

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

59

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt12

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Tests18pt80

Test files detected (.github/workflows/tests).

CI/CD14pt100

CI is configured (.github/workflows/build-registry.yml).

Project health

89

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (.github/workflows/pyproject.toml).

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)
  • 182
    Forks
  • 851
    Releaseslatest 7mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 257
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 13h
    Median PR merge time
  • 81
    Open issues
Repository files53 root entries
  • .github
    Good: Test files detected (.github/workflows/tests).
    Good: CI is configured (.github/workflows/build-registry.yml).
    Good: Dependabot configured for github-actions.
    Good: Dependency manifest found (.github/workflows/pyproject.toml).
  • .protocol-matrix
  • agoragentic-acp
  • amp-acp
  • auggie
  • autohand
  • claude-acp
  • cline
  • codebuddy-code
  • codex-acp
  • cortex-code
  • corust-agent
  • crow-cli
  • cursor
  • deepagents
  • devin
  • dimcode
  • dirac
  • factory-droid
  • fast-agent
  • gemini
  • github-copilot
  • github-copilot-cli
  • glm-acp-agent
  • goose
  • grok-build
  • junie
  • kilo
  • kimi
  • minion-code
  • mistral-vibe
  • nova
  • opencode
  • pi-acp
  • poolside
  • qoder
  • qwen-code
  • sigit
  • stakpak
  • vtcode
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • agent.schema.json
  • AGENTS.md
  • AUTHENTICATION.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    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.
  • FORMAT.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • quarantine.json
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • registry.schema.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/agentclientprotocol/registry)](https://www.repo-grade.com/report/agentclientprotocol/registry)

More graded repos