Good community traction and solid fundamentals. Nearly in the top tier.

Documentation

73

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.

README12pt70

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

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 (backend-java/src/test).

Reproducibility6pt80

Lockfile present (frontend/package-lock.json). Installs are reproducible.

CI/CD14pt100

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

Linting and formatting5pt100

Java/Kotlin linting configured (frontend/.eslintrc.json).

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 (backend-java/pom.xml).

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

Community

  • Community health
  • authors own >50% of commits
  • 1,072
    Watchers

Responsiveness

  • Median issue response
  • 2h
    Median PR merge time
  • 1
    Open issues
Repository files15 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • backend
  • backend-java
    Good: Test files detected (backend-java/src/test).
    Good: Environment pinned via backend-java/Dockerfile.
    Good: Dependency manifest found (backend-java/pom.xml).
  • docker
  • docs
  • frontend
    Good: Java/Kotlin linting configured (frontend/.eslintrc.json).
    Good: Lockfile present (frontend/package-lock.json). Installs are reproducible.
  • scripts
  • .gitignore
    Good: .gitignore present.
  • demo-input.html
  • demo-inputnumber.html
  • docker-compose.yml
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • 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.
    Good: README documents how to run the project.
  • README.zh-CN.md