Good shape overall. A few tweaks would push it into the top tier.

Global MapleStory Server BeiDou(冒险岛GMS服务端北斗)

Documentation

58

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 instructions9pt45

README documents how to install the project.

README12pt70

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

72

CI/CD14pt40

CI is configured (.github/workflows/ai-pr-review.yml).

Reproducibility6pt70

Lockfile present (gms-ui/pnpm-lock.yaml). Installs are reproducible.

Tests18pt80

Test files detected (gms-server/src/test).

Linting and formatting5pt100

Java/Kotlin linting configured (gms-ui/.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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)
  • 335
    Forks
  • 9
    Releaseslatest 24d ago

Community

  • Community health
  • authors own >50% of commits
  • 538
    Watchers

Responsiveness

  • 9h
    Median issue response
  • 6h
    Median PR merge time
  • 30
    Open issues
Repository files7 root entries
  • .github
    Good: CI is configured (.github/workflows/ai-pr-review.yml).
    Good: Issue or PR templates present.
  • gms-server
    Good: Test files detected (gms-server/src/test).
  • gms-ui
    Good: Java/Kotlin linting configured (gms-ui/.eslintrc.js).
    Good: Lockfile present (gms-ui/pnpm-lock.yaml). Installs are reproducible.
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
    Good: README has code examples.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.