bannerlord-coop-team/bannerlordcoop

0

/ 100

Documentation56
Engineering67
Health84
C#334Other1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Documentation

56

Contributing guide5pt25

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.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt55

README is present.

License6pt100

Licensed under Other.

Engineering

67

Linting and formatting5pt0

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

Tests18pt80

Test files detected (source/Common.Tests/Extensions/FastInvokeTests.cs).

CI/CD14pt85

CI is configured (.github/workflows/build_test_server.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

84

Repository metadata5pt40

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 manifest6pt100

Dependency manifest found (source/ClientDebug 2/ClientDebug2.csproj).

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)
  • 67
    Forks
  • 1
    Releaseslatest 3y ago

Community

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

Responsiveness

  • 15h
    Median issue response
  • 1d 5h
    Median PR merge time
  • 135
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/build_test_server.yml).
    Good: Issue or PR templates present.
  • deploy
  • doc
  • Images
  • source
    Good: Test files detected (source/Common.Tests/Extensions/FastInvokeTests.cs).
    Good: Dependency manifest found (source/ClientDebug 2/ClientDebug2.csproj).
  • UIMovies
  • Workshop
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • config_coop.json
  • config_missions.json
  • deploy.ps1
  • Deploy.targets
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • DockerPrepare.ps1
  • LICENSE
    Good: Licensed under Other.
  • NOTICE.md
  • prepare-links.ps1
  • README.md
    Good: 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