89
/ 100
Polished and well engineered. Punching above its star count.
Benchmarking Goal-Oriented Software Engineering
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
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
100
README is present.
README documents how to install the project.
Licensed under MIT.
Contributing guide is detailed and thorough.
Engineering
79
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.
Lockfile present (uv.lock). Installs are reproducible.
Test files detected (configs/test).
CI is configured (.github/workflows/check-links.yaml).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Project health
98
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 4 / 7Commits (30d / 90d)
- 17Forks
- 0Releases
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 173Watchers
Responsiveness
- 5d 19hMedian issue response
- 13hMedian PR merge time
- 15Open issues
Repository files16 root entries
- .githubGood: Code of conduct present.Good: CI is configured (.github/workflows/check-links.yaml).
- codeclash
- configsGood: Test files detected (configs/test).
- docsGood: Security policy present.
- scripts
- tests
- .env.example
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under MIT.
- main.py
- mkdocs.yml
- 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.
- 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/codeclash-ai/codeclash)