lunarclient/servermappings

0

/ 100

Documentation39
Engineering47
Health100
Python200MIT1d ago
Grade a repo

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

Public mapping of Minecraft server IPs <-> a pretty display name

Documentation

39

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

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.

README12pt55

README is present.

License6pt100

Licensed under MIT.

Engineering

47

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (.scripts/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.pylintrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (.scripts/requirements.txt).

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)
  • 1,947
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 1d 1h
    Median issue response
  • 11h
    Median PR merge time
  • 2
    Open issues
Repository files13 root entries
  • .github
    Good: CI is configured (.github/workflows/docs.yml).
    Good: Issue or PR templates present.
  • .scripts
    Good: Lockfile present (.scripts/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (.scripts/requirements.txt).
  • .vscode
  • docs
  • servers
  • .gitignore
    Good: .gitignore present.
  • .pylintrc
    Good: Linter or formatter configured (.pylintrc).
  • inactive.json
  • inactive.schema.json
  • LICENSE
    Good: Licensed under MIT.
  • metadata.example.json
  • metadata.schema.json
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.