0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Persist and reuse KV Cache to speedup your LLM.
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.
- 2README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 3Install and run instructions9pt
Add a section showing how to install dependencies.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
64
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
80
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.
Test files detected (benchmarks/logging_perf_test.py).
Lockfile present (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/lint-and-test.yml).
Issue or PR templates present.
Project health
100
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
- -Commits (30d / 90d)
- 86Forks
- 11Releaseslatest 4mo ago
Community
- -Community health
- -authors own >50% of commits
- 293Watchers
Responsiveness
- 16hMedian issue response
- <1hMedian PR merge time
- 69Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/lint-and-test.yml).Good: Issue or PR templates present.
- benchmarksGood: Test files detected (benchmarks/logging_perf_test.py).
- docker
- docs
- examples
- scripts
- testGood: Environment pinned via test/runner-docker/Dockerfile.
- ucm
- .clang-format
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .readthedocs.yaml
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- format.sh
- LICENSEGood: Licensed under MIT.
- MANIFEST.in
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README_zh.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.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.
- README.md
- requirements-lint.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- setup.py
- ucm_patch.pth
- version.ini
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/modelengine-group/unified-cache-management)