mitchross/talos-argocd-proxmox

0

/ 100

Documentation96
Engineering18
Health68
Python751d ago
Grade a repo

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

Talos ArgoCD Homelab. My personal production Cluster.

Documentation

96

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

A license file is present.

Engineering

18

Tests18pt0

No tests detected anywhere in the repository.

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

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

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/cluster-ci.yml).

Project health

68

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 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

  • —
    Community health
  • —
    authors own >50% of commits
  • 75
    Watchers

Responsiveness

  • 19d 22h
    Median issue response
  • 1d 12h
    Median PR merge time
  • 3
    Open issues
Repository files21 root entries
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/cluster-ci.yml).
  • .vscode
  • benchmarks
  • docs
  • hack
  • infrastructure
  • monitoring
  • my-apps
    Good: Environment pinned via my-apps/development/radar-ng/basemap-bootstrap-image/Dockerfile.
  • omni
    Good: A license file is present.
    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.
  • scripts
  • .codex
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • AGENTS.md
  • CLAUDE.md
  • firewalla-dns-config.txt
  • mkdocs.yml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.