jfalcou/kumi
Grade a repo

0

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

C++20 Compact Tuple Tools

Documentation82
Engineering62
Health68
C++60BSL-1.0today

Documentation

82

Contributing guide5pt5

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under BSL-1.0.

Engineering

62

Linting and formatting5pt0

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt72

CI is configured (.github/workflows/ci.yml).

Tests18pt80

Test files detected (.github/actions/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

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 metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 10
    Forks
  • 6
    Releaseslatest 2mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 60
    Watchers

Responsiveness

  • 43d 14h
    Median issue response
  • 1h
    Median PR merge time
  • 4
    Open issues
Repository files13 root entries
  • .github
    Good: 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
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • CMakeLists.txt
  • CMakePresets.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • LICENSE.md
    Good: Licensed under BSL-1.0.
  • README.md
    Good: 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.