Good community traction and solid fundamentals. Nearly in the top tier.

The definitive list of the best of (consumer facing) open source.

Documentation

82

README12pt70

README is present.

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

73

CI/CD14pt40

CI is configured (.github/workflows/format-maintenance.yml).

Tests18pt80

Test files detected (core/tests).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (core/ruff.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (apps/cli/go.mod).

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)
  • 126
    Forks
  • 8
    Releaseslatest 5mo ago

Community

  • Community health
  • authors own >50% of commits
  • 3,278
    Watchers

Responsiveness

  • 12h
    Median issue response
  • 5h
    Median PR merge time
  • 10
    Open issues
Repository files9 root entries
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/format-maintenance.yml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • apps
    Good: Dependency manifest found (apps/cli/go.mod).
  • assets
  • core
    Good: Test files detected (core/tests).
    Good: Linter or formatter configured (core/ruff.toml).
    Good: Lockfile present (core/uv.lock). Installs are reproducible.
    Good: Environment pinned via core/.python-version.
  • resources
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under MIT.
  • README.md
    Good: 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.