60
/ 100
Strong community interest, but docs and engineering haven't caught up to the hype.
An MCP-based chatbot | 一个基于MCP的聊天机器人
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (87).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
72
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 MIT.
Engineering
37
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/build.yml).
Lockfile present (scripts/Image_Converter/requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (scripts/Image_Converter/requirements.txt).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 13 / 50Commits (30d / 90d)
- 6,297Forks
- 64Releaseslatest 1y ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 27,967Watchers
Responsiveness
- 17hMedian issue response
- 5hMedian PR merge time
- 656Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- docs
- main
- partitions
- scriptsGood: Lockfile present (scripts/Image_Converter/requirements.txt). Installs are reproducible.Good: Dependency manifest found (scripts/Image_Converter/requirements.txt).
- .clang-format
- .gitignoreGood: .gitignore present.
- CMakeLists.txt
- LICENSEGood: Licensed under MIT.
- README_ja.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.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.md
- README.md
- sdkconfig.defaults
- sdkconfig.defaults.esp32
- sdkconfig.defaults.esp32c3
- sdkconfig.defaults.esp32c5
- sdkconfig.defaults.esp32c6
- sdkconfig.defaults.esp32p4
- sdkconfig.defaults.esp32s3
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/78/xiaozhi-esp32)