0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
multi-depth architecture views for code understanding and generation in extremely fast speed
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Link to a deployed version, docs site, or demo video. Users want to see it running.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
84
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 (Cargo.lock). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/ci.yml).
Rust linting configured (.eslintrc.json, cargo clippy in CI, cargo fmt in CI).
Project health
100
Dependency manifest found (Cargo.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
- -Commits (30d / 90d)
- 9Forks
- 35Releaseslatest 9mo ago
Community
- -Community health
- -authors own >50% of commits
- 98Watchers
Responsiveness
- 7hMedian issue response
- <1hMedian PR merge time
- 14Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- crates
- doc
- npm
- scripts
- testsGood: Test files detected (tests).
- third_party
- .eslintrc.jsonGood: Rust linting configured (.eslintrc.json, cargo clippy in CI, cargo fmt in CI).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .llmccignore
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- justfile
- LICENSEGood: Licensed under Apache-2.0.
- 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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.Good: README documents how to install the project.Good: README documents how to run the project.
- rustfmt.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/allenanswerzq/llmcc)