mrwulf/home-cluster
Grade a repo

0

/ 100

GradeF

Getting some notice. Tests and CI would be the fastest wins.

Documentation70
Engineering40
Health53
JavaScript14MITtoday

Documentation

70

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 instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

40

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/lint.yaml).

Linting and formatting5pt100

Linter or formatter configured (.github/linters/.prettierrc.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

53

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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.

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

Community

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

Responsiveness

  • -
    Median issue response
  • 19h
    Median PR merge time
  • 6
    Open issues
Repository files21 root entries
  • .agents
  • .github
    Good: CI is configured (.github/workflows/lint.yaml).
    Good: Linter or formatter configured (.github/linters/.prettierrc.yaml).
    Good: Issue or PR templates present.
  • .taskfiles
  • cluster
  • docs
  • monitoring
  • pxe-files
  • scripts
  • talos
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaksignore
  • .pre-commit-config.yaml
  • .sops.yaml
  • CLAUDE.md
  • LICENSE
    Good: Licensed under MIT.
  • mise.toml
    Good: Environment pinned via mise.toml.
  • 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.
  • Taskfile.yml
  • TO-DO.md