withmartian/code-review-benchmark

0

/ 100

Documentation88
Engineering68
Health84
Python192MIT1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Documentation

88

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

68

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.

Issue and PR templates6pt0

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.

Tests18pt80

Test files detected (offline/tests).

Reproducibility6pt80

Lockfile present (offline/uv.lock). Installs are reproducible.

CI/CD14pt100

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

Project health

84

Repository metadata5pt40

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 manifest6pt100

Dependency manifest found (offline/pyproject.toml).

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)
  • 34
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 192
    Watchers

Responsiveness

  • 22d 22h
    Median issue response
  • 19h
    Median PR merge time
  • 13
    Open issues
Repository files8 root entries
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
  • images
  • methodology
  • offline
    Good: Test files detected (offline/tests).
    Good: Lockfile present (offline/uv.lock). Installs are reproducible.
    Good: Dependency manifest found (offline/pyproject.toml).
  • online
    Good: Environment pinned via online/api_service/Dockerfile.
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under MIT.
  • 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.