grumpycoders/pcsx-redux

0

/ 100

Documentation93
Engineering69
Health100
C++945GPL-2.01d ago
Grade a repo

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

The PCSX-Redux project is a collection of tools, research, hardware design, and libraries aiming at development and reverse engineering on the PlayStation 1. The core product itself, PCSX-Redux, is yet another fork of the Playstation emulator, PCSX.

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under GPL-2.0.

Engineering

69

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/linux-build.yml).

Tests18pt80

Test files detected (src/mips/tests).

Linting and formatting5pt100

Linter or formatter configured (src/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (tools/vscode-extension/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)
  • 141
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 3d 20h
    Median issue response
  • <1h
    Median PR merge time
  • 149
    Open issues
Repository files43 root entries
  • .github
    Good: CI is configured (.github/workflows/linux-build.yml).
    Good: Issue or PR templates present.
  • .vscode
  • hardware
  • i18n
  • resources
  • src
    Good: Test files detected (src/mips/tests).
    Good: Linter or formatter configured (src/.editorconfig).
  • tests
  • third_party
  • tools
    Good: Environment pinned via tools/build-cross/Dockerfile.
    Good: Dependency manifest found (tools/vscode-extension/package.json).
  • vsprojects
  • .coderabbit.yaml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mailmap
  • AppImageBuilder.yml
  • AUTHORS
  • azure-pipelines-cli.yml
  • azure-pipelines-linux.yml
  • azure-pipelines-vsce.yml
  • azure-pipelines.yml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • compile_flags.txt
  • 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.
    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.
  • cross-env.list
  • crowdin.yml
  • distcc-make.sh
  • dockermake-cross.bat
  • dockermake-cross.sh
  • dockermake.bat
  • dockermake.sh
  • dockershell.bat
  • dockershell.sh
  • env.list
  • flake.lock
  • flake.nix
  • LICENSE
    Good: Licensed under GPL-2.0.
  • LICENSES.md
  • Makefile
  • mips.ps1
  • pcsx-redux.nix
  • 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.
  • TODO.md