73
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Build your own clan [read-only mirror of https://git.clan.lol/clan/clan-core]
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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
76
README is present.
CONTRIBUTING guide found.
README documents how to install the project.
Licensed under MIT.
Engineering
61
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.
CI is configured (.github/workflows/repo-sync.yml).
Test files detected (clanServices/admin/tests).
Lockfile present (pkgs/clan-app/ui/package-lock.json). Installs are reproducible.
Linter or formatter configured (pkgs/clan-app/ui/eslint.config.ts).
Project health
100
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 90 / 474Commits (30d / 90d)
- 16Forks
- 0Releases
Community
- 50% - FairCommunity health
- 2 bus factorauthors own >50% of commits
- 166Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 1Open issues
Repository files32 root entries
- .gitea
- .githubGood: CI is configured (.github/workflows/repo-sync.yml).Good: Dependabot configured for github-actions.
- checks
- clanServicesGood: Test files detected (clanServices/admin/tests).
- darwinModules
- devFlake
- docsGood: 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.
- flakeModules
- lib
- machines
- modules
- nixosModules
- pkgsGood: Linter or formatter configured (pkgs/clan-app/ui/eslint.config.ts).Good: Lockfile present (pkgs/clan-app/ui/package-lock.json). Installs are reproducible.
- scripts
- sops
- templates
- vars
- _typos.toml
- .envrc
- .gitignoreGood: .gitignore present.
- .rumdl.toml
- apps.nix
- CODEOWNERS
- devShell.nix
- flake.lock
- flake.nix
- formatter.nix
- inventory.json
- LICENSE.mdGood: Licensed under MIT.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.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.
- VERSION
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/clan-lol/clan-core)