zengm-games/zengm

0

/ 100

Documentation65
Engineering84
Health94
TypeScript450Other1d ago
Grade a repo

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

Basketball GM (and other ZenGM games) are single-player sports management simulation games, made entirely in client-side JavaScript.

Documentation

65

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.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

84

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 (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (src/common/applyRealTeamInfo.test.ts).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

94

Dependency manifest6pt82

Dependency manifest found (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)
  • 207
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 6h
    Median issue response
  • 2h
    Median PR merge time
  • 99
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/nodejs.yml).
  • .husky
  • analysis
  • data
  • public
  • src
    Good: Test files detected (src/common/applyRealTeamInfo.test.ts).
  • tools
  • .browserslistrc
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .oxfmtrc.json
  • CHANGELOG.md
  • CLA-entity.md
  • CLA-individual.md
  • eslint.config.js
  • LICENSE.md
    Good: Licensed under Other.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • TODO
  • tsconfig.base.json
  • tsconfig.json
  • tsconfig.node.json
  • tsconfig.web.json
  • vitest.config.ts