phantomptr/ps5upload
Grade a repo

95

/ 100

GradeA

Exemplary work. Strong across project hygiene, documentation, and engineering.

Top 6% of 5,156 graded repos

Send games, apps and homebrew to a jailbroken PS5, and manage the console from your computer, phone or browser.

Documentation94
Engineering93
Health100
TypeScript780Other24d ago

Outstanding. A score of 95/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

5 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
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

  4. 4
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

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

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

93

Tests18pt80

Test files detected (client/e2e/bug-report-captures.spec.ts).

CI/CD14pt100

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

Linting and formatting5pt100

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

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 58
    Forks
  • 68
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • 1d 16h
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files28 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/engine-ci.yml).
    Good: Dependabot covers 5 ecosystems (cargo, cargo, npm, github-actions, docker). Dependencies stay current.
    Good: Issue or PR templates present.
  • bench
  • client
    Good: Test files detected (client/e2e/bug-report-captures.spec.ts).
    Good: Linter or formatter configured (client/eslint.config.mjs).
  • engine
    Good: Environment pinned via engine/Dockerfile.
  • LICENSES
  • payload
  • protocol
  • scripts
  • site
  • tests
  • third_party
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • DISCLAIMER.md
  • FAQ.md
  • LICENSE
    Good: Licensed under Other.
  • logo.png
  • Makefile
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
  • SECURITY.md
    Good: Security policy present.
  • TESTING.md
  • VERSION
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/phantomptr/ps5upload)](https://www.repo-grade.com/report/phantomptr/ps5upload)

More graded TypeScript repos