0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
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 C (78).
See your top fixesTop 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
56
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under Other.
Engineering
67
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
Test files detected (source/Common.Tests/Extensions/FastInvokeTests.cs).
CI is configured (.github/workflows/build_test_server.yml).
Issue or PR templates present.
Project health
84
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.
Dependency manifest found (source/ClientDebug 2/ClientDebug2.csproj).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 67Forks
- 1Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 334Watchers
Responsiveness
- 15hMedian issue response
- 1d 5hMedian PR merge time
- 135Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/build_test_server.yml).Good: Issue or PR templates present.
- deploy
- doc
- Images
- sourceGood: Test files detected (source/Common.Tests/Extensions/FastInvokeTests.cs).Good: Dependency manifest found (source/ClientDebug 2/ClientDebug2.csproj).
- UIMovies
- Workshop
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- config_coop.json
- config_missions.json
- deploy.ps1
- Deploy.targets
- DockerfileGood: Environment pinned via Dockerfile.
- DockerPrepare.ps1
- LICENSEGood: Licensed under Other.
- NOTICE.md
- prepare-links.ps1
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- runmefirst.cmd
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/bannerlord-coop-team/bannerlordcoop)