msonrm/quubee
Grade a repo

0

/ 100

GradeF

Just launched. Invest in a README, license, and CI from day one.

QuuBee — PC-98 フリーソフトのブラウザプレイヤー (著作権クリーン: NEC BIOS/MS-DOS 不使用)

Documentation32
Engineering9
Health100
JavaScript7Othertoday

Documentation

32

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.

README12pt35

README is present.

License6pt100

Licensed under Other.

Engineering

9

Tests18pt0

No tests detected anywhere in the repository.

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

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt70

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (tools/font_build/package.json).

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

Community

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

Responsiveness

  • 6h
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files17 root entries
  • core
  • docs
  • emscripten
  • games
  • licenses
  • native
  • tools
    Good: Lockfile present (tools/font_build/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (tools/font_build/package.json).
  • web
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CHANGELOG.md
  • CLAUDE.md
  • CREDITS.md
  • LICENSE
    Good: Licensed under Other.
  • LICENSE-MIT
  • 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.
  • TODO.md