0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
基于全新架构的 不思议迷宫 小助手。图像技术 + 模拟控制,解放双手! 由 MaaFramework 强力驱动!
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 (86).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 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
63
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
60
Test files detected (assets/resource/test).
CI is configured (.github/workflows/check.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Linter or formatter configured (.prettierrc).
Issue or PR templates present.
Project health
86
Dependency manifest found (package.json).
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)
- 25Forks
- 164Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 54Watchers
Responsiveness
- 7hMedian issue response
- 1hMedian PR merge time
- 12Open issues
Repository files21 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/check.yml).Good: Issue or PR templates present.
- .vscode
- agent
- assetsGood: Test files detected (assets/resource/test).
- deps
- docs
- intelligence_data
- tools
- .gitignoreGood: .gitignore present.
- .gitmodules
- .mcp.json
- .pre-commit-config.yaml
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- LICENSEGood: Licensed under MIT.
- logo.png
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.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.
- requirements.txt
- TodoList.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/khazixw2/maagumballs)