0

/ 100

GradeD

Getting some notice. Tests and CI would be the fastest wins.

Top 48% of 5,156 graded repos

MMO server cluster in Elixir test.

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 (88).

See your top fixes
Now
D
68
Potential
B
88

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  3. 3
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  4. 4
    README12pt

    Link to a deployed version, docs site, or demo video. Users want to see it running.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

35

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt10

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

Add a section showing how to install dependencies.

README12pt35

README is present.

License6pt100

Licensed under MIT.

Engineering

78

Issue and PR templates6pt0

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.

Tests18pt80

Test files detected (apps/auth_server/test).

Reproducibility6pt80

Lockfile present (apps/scene_server/native/field_kernel/Cargo.lock). Installs are reproducible.

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (clients/web_client/.prettierrc.json).

Project health

100

Dependency manifest6pt100

Dependency manifest found (apps/scene_server/native/field_kernel/Cargo.toml).

Repository metadata5pt100

Repository has a description.

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)
  • 2
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 18
    Watchers

Responsiveness

  • 105d 4h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .omc
  • apps
    Good: Test files detected (apps/auth_server/test).
    Good: Lockfile present (apps/scene_server/native/field_kernel/Cargo.lock). Installs are reproducible.
    Good: Dependency manifest found (apps/scene_server/native/field_kernel/Cargo.toml).
  • clients
    Good: Linter or formatter configured (clients/web_client/.prettierrc.json).
  • config
  • deploy
  • docs
  • scripts
  • .dockerignore
  • .formatter.exs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .tool-versions
  • AGENTS.md
  • CLAUDE.md
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE
    Good: Licensed under MIT.
  • mix.exs
  • mix.lock
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/dyzdyz010/ex_mmo_cluster)](https://www.repo-grade.com/report/dyzdyz010/ex_mmo_cluster)

More graded Elixir repos