52
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Talos ArgoCD Homelab. My personal production Cluster.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (82).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
96
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
A license file is present.
Engineering
18
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/cluster-ci.yml).
Project health
68
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 has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 22Forks
- 0Releases
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 76Watchers
Responsiveness
- 19d 22hMedian issue response
- 1d 12hMedian PR merge time
- 3Open issues
Repository files21 root entries
- .claude
- .githooks
- .githubGood: CI is configured (.github/workflows/cluster-ci.yml).
- .vscode
- benchmarks
- docs
- hack
- infrastructure
- monitoring
- my-appsGood: Environment pinned via my-apps/development/radar-ng/basemap-bootstrap-image/Dockerfile.
- omniGood: 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
- .gitignoreGood: .gitignore present.
- .mcp.json
- AGENTS.md
- CLAUDE.md
- firewalla-dns-config.txt
- mkdocs.yml
- README.mdGood: 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mitchross/talos-argocd-proxmox)