91
/ 100
Polished and well engineered. Punching above its star count.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
93
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
92
Lockfile present (uv.lock). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Test files detected (examples/plugins/cao-discord/tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Issue or PR templates present.
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (pyproject.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 32 / 118Commits (30d / 90d)
- 140Forks
- 12Releaseslatest 3mo ago
Community
- 75% - GoodCommunity health
- 3 bus factorauthors own >50% of commits
- 738Watchers
Responsiveness
- 2d 16hMedian issue response
- 17hMedian PR merge time
- 51Open issues
Repository files25 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- docs
- examplesGood: Test files detected (examples/plugins/cao-discord/tests).
- scripts
- skills
- src
- test
- web
- .gitignoreGood: .gitignore present.
- .tmux.conf
- CHANGELOG.md
- cliff.toml
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CODEBASE.md
- CONTRIBUTING.mdGood: 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.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- DEVELOPMENT.md
- LICENSEGood: Licensed under Apache-2.0.
- mypy.ini
- NOTICE
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.
- SECURITY.mdGood: Security policy present.
- tmux-install.sh
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/awslabs/cli-agent-orchestrator)