0

/ 100

GradeA

Excellent work. The main thing left to polish is CI. It just hasn't found an audience yet.

Top 12% of 5,156 graded repos
TypeScript0AGPL-3.010d ago

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

  4. 4
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

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

100

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

92

CI/CD14pt72

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

Tests18pt100

Test files detected (packages/api/src/__tests__).

Linting and formatting5pt100

Linter or formatter configured (eslint.config.mjs).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

67

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.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

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

Community

  • 85% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 0
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 5
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/dictionaries) (−40 pts).Fix: Remove them and add to .gitignore.
  • data
  • docs
  • migrations
  • packages
    Good: Test files detected (packages/api/src/__tests__).
  • scripts
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • API_GUIDE.md
  • ARCHITECTURE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • crowdin.yml
  • DEPLOYMENT.md
  • docker-compose.local.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • Dockerfile.api
  • Dockerfile.bot
  • Dockerfile.dashboard
  • ENVIRONMENT.md
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • LOCALIZATION.md
  • MIGRATIONS.md
  • 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.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SCHEMA.md
  • SECURITY.md
    Good: Security policy present.
  • TESTING.md
  • TROUBLESHOOTING.md
  • tsconfig.json
  • TYPESCRIPT.md
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/zeffuro/fakegaming-bot)](https://www.repo-grade.com/report/zeffuro/fakegaming-bot)

More graded TypeScript repos