studie-tech/theninjarpg
Grade a repo

0

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 14% of 5,156 graded repos

Source code for TheNinja-RPG Core 4

Documentation85
Engineering90
Health94
TypeScript1001mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  3. 3
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

85

README12pt70

README is present.

Contributing guide5pt73

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

A license file is present.

Engineering

90

Tests18pt80

Test files detected (app/src/libs/__tests__).

Reproducibility6pt80

Lockfile present (app/bun.lock). Installs are reproducible.

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (app/biome.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (app/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 31
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 24d 7h
    Median issue response
  • <1h
    Median PR merge time
  • 67
    Open issues
Repository files24 root entries
  • .claude
  • .devcontainer
    Good: Environment pinned via .devcontainer/docker-compose.yml.
    Issue: Build artifacts or local files may be committed (.devcontainer/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • .github
    Good: CI is configured (.github/workflows/test_build.yml).
    Good: Issue or PR templates present.
  • .husky
  • .openhands
  • .vscode
  • app
    Good: Test files detected (app/src/libs/__tests__).
    Good: Linter or formatter configured (app/biome.json).
    Good: Lockfile present (app/bun.lock). Installs are reproducible.
    Good: Dependency manifest found (app/package.json).
  • assets
    Good: A license file is present.
  • docs
  • scripts
  • soketi
  • spacetimedb-towerdefense
  • .cursorrules
  • .eslintignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .openhands_instructions
  • biome.json
  • CLAUDE.md
  • CODEOWNERS
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEVELOPMENT.md
  • 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.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/studie-tech/theninjarpg)](https://www.repo-grade.com/report/studie-tech/theninjarpg)

More graded TypeScript repos