0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
C++20 Compact Tuple Tools
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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
82
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 documents how to install the project.
README is present.
Licensed under BSL-1.0.
Engineering
62
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/ci.yml).
Test files detected (.github/actions/test).
Issue or PR templates present.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 10Forks
- 6Releaseslatest 3mo ago
Community
- -Community health
- -authors own >50% of commits
- 60Watchers
Responsiveness
- 43d 14hMedian issue response
- 1hMedian PR merge time
- 4Open issues
Repository files13 root entries
- .githubGood: Test files detected (.github/actions/test).Good: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- cmake
- doc
- include
- test
- .clang-format
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- CMakeLists.txt
- CMakePresets.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- LICENSE.mdGood: Licensed under BSL-1.0.
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/jfalcou/kumi)