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

Discover and compare open-source Agent Skills, tools & MCP servers — with quality scoring, trending analysis, and automated GitHub sync

Documentation

54

License6pt0

No license detected.

Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

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.

README12pt70

README is present.

Install and run instructions9pt100

README documents how to install the project.

Engineering

73

CI/CD14pt40

CI is configured (.github/workflows/daily-report.yml).

Tests18pt80

Test files detected (backend/test_newsletter.py).

Reproducibility6pt80

Lockfile present (backend/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (frontend/eslint.config.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (backend/requirements.txt).

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

Community

  • Community health
  • authors own >50% of commits
  • 297
    Watchers

Responsiveness

  • Median issue response
  • Median PR merge time
  • 5
    Open issues
Repository files13 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/daily-report.yml).
    Good: Issue or PR templates present.
  • backend
    Good: Test files detected (backend/test_newsletter.py).
    Good: Lockfile present (backend/requirements.txt). Installs are reproducible.
    Good: Environment pinned via backend/Dockerfile.
    Good: Dependency manifest found (backend/requirements.txt).
  • docs
  • frontend
    Good: Linter or formatter configured (frontend/eslint.config.js).
  • memory
  • ops
  • supabase
  • .gitignore
    Good: .gitignore present.
  • CLAUDE.md
  • CONTEXT.md
  • 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.