moonladderstudios/moonmind
Grade a repo

0

/ 100

GradeC

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

Run Claude Code and Codex with superior safety, resiliency, and observability.

Documentation72
Engineering76
Health100
Python11MITtoday

Documentation

72

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.

License6pt100

Licensed under MIT.

Engineering

76

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 (api_service/test_ui_route.py).

CI/CD14pt85

CI is configured (.github/workflows/pentestgpt-runner.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (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)
  • 4
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 89d 12h
    Median issue response
  • <1h
    Median PR merge time
  • 54
    Open issues
Repository files49 root entries
  • .agents
  • .codex
    Good: Licensed under MIT.
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/pentestgpt-runner.yml).
    Good: Dependabot covers 4 ecosystems (pip, pip, docker, github-actions). Dependencies stay current.
  • .specify
  • api_service
    Good: Test files detected (api_service/test_ui_route.py).
    Good: Environment pinned via api_service/Dockerfile.
  • artifacts-root-owned-context
  • artifacts-root-owned-readonly
  • config
  • deploy
  • docker
  • docs
  • examples
  • frontend
  • init_db
  • init_db_scripts
  • keycloak
  • memory
  • moonmind
  • samples
  • scripts
  • services
  • tests
  • tools
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env-template
  • .env.vllm-template
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .npmignore
  • .pre-commit-config.yaml
  • AGENTS.md
  • CLAUDE.md
  • config.toml
  • docker-compose.downloader.yaml
  • docker-compose.test.yaml
  • docker-compose.yaml
  • GEMINI.md
  • LICENSE
  • manifest.schema.json
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • poetry.lock
  • postcss.config.cjs
  • pyproject.toml
  • 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.
  • tailwind.config.cjs