0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
AI-native agent harness for coding workflows by python: multi-model LLM orchestration, stateful sessions, tool governance, traceable delivery, and provider routing for GPT, Claude, DeepSeek, Qwen, Kimi, GLM, and MiniMax.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Link to a deployed version, docs site, or demo video. Users want to see it running.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 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
77
README is present.
CONTRIBUTING guide found.
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 (uv.lock). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/ai-quality.yml).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Project health
93
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)
- 67Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 294Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 22Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/ai-quality.yml).
- backups
- docsGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- examples
- scenarios
- scripts
- spikes
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- AGENTS.md
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- NOTICE
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- README.zh-CN.md
- THIRD_PARTY_NOTICES.md
- 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/zhnt/loushang)