0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
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
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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
73
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 Other.
Engineering
78
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.
Test files detected (backend-java/src/test).
Lockfile present (frontend/package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Java/Kotlin linting configured (frontend/.eslintrc.json).
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (backend-java/pom.xml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 108Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 1,072Watchers
Responsiveness
- -Median issue response
- 2hMedian PR merge time
- 1Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- backend
- backend-javaGood: Test files detected (backend-java/src/test).Good: Environment pinned via backend-java/Dockerfile.Good: Dependency manifest found (backend-java/pom.xml).
- docker
- docs
- frontendGood: Java/Kotlin linting configured (frontend/.eslintrc.json).Good: Lockfile present (frontend/package-lock.json). Installs are reproducible.
- scripts
- .gitignoreGood: .gitignore present.
- demo-input.html
- demo-inputnumber.html
- docker-compose.yml
- LICENSEGood: Licensed under Other.
- Makefile
- 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.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-CN.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/emiyaaaaa/hivemind)