0
/ 100
Well engineered. The main gaps are issue and PR templates and a contributing guide. Impressive for a brand-new repo.
Opinionated LiteLLM operator stack: console plus a shared API, with memory, privacy, safety, and spend limits.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.
- 3Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 4Dependency manifest6pt
Add `authors = [...]` under [project] so the package has clear ownership.
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
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
85
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 (requirements.txt). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/ci.yml).
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
- -Commits (30d / 90d)
- 0Forks
- 1Releaseslatest 8d ago
Community
- 57% - FairCommunity health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- app
- assets
- docs
- env
- prompts
- testsGood: Test files detected (tests).
- web
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- compose.yaml
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under MIT.
- 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.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.
- requirements-dev.txt
- requirements-pii.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- SECURITY.mdGood: Security policy present.
- USAGE_WALKTHROUGH.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/m1ndsmith/reallm)