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

Turn your blogs to videos, while retaining your voice

Documentation

53

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

78

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 (backend/conftest.py).

Reproducibility6pt80

Lockfile present (backend/mcp_server/ui_src/package-lock.json). Installs are reproducible.

CI/CD14pt100

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

Linting and formatting5pt100

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (backend/mcp_server/ui_src/package.json).

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

Community

  • 25% - Weak
    Community health
  • authors own >50% of commits
  • 113
    Watchers

Responsiveness

  • Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files16 root entries
  • .github
    Good: CI is configured (.github/workflows/backend-tests.yml).
  • backend
    Good: Test files detected (backend/conftest.py).
    Good: Lockfile present (backend/mcp_server/ui_src/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (backend/mcp_server/ui_src/package.json).
  • blogs
  • frontend
    Good: Linter or formatter configured (frontend/eslint.config.js).
  • remotion-video
  • scripts
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • anthropic.svg
  • Crafted_template_guide.md
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • gemini-color.svg
  • openai.png
  • progress.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.