0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
🐹 A free, open-source, native macOS GUI for the Mole CLI (mo): clean, uninstall, optimize, analyze disk, and watch live status. Plus long-range history + an MCP server for AI agents. Coming to Windows
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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.
Licensed under MIT.
Engineering
62
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.
Lockfile present (windows/Assets/Mole/go.sum). Installs are reproducible.
Test files detected (macos/Tests).
CI is configured (.github/workflows/ci.yml).
Project health
100
Dependency manifest found (windows/Assets/Mole/go.mod).
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)
- 139Forks
- 12Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 739Watchers
Responsiveness
- 4hMedian issue response
- 19hMedian PR merge time
- 4Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- brand
- docs
- macosGood: Test files detected (macos/Tests).
- packaging
- plans
- Properties
- scripts
- windowsGood: 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.Good: Lockfile present (windows/Assets/Mole/go.sum). Installs are reproducible.Good: Dependency manifest found (windows/Assets/Mole/go.mod).
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- 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.
- RELEASES.md
- SECURITY.mdGood: Security policy present.
- TELEMETRY.md
- wrangler.jsonc
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/caezium/burrow)