Popular for its size, but the engineering basics lag behind the interest.

Optimized/rewritten Nintendo 64 emulator made specifically for Libretro. Originally based on Mupen64 Plus.

Documentation

33

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

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.

README12pt38

README is present.

License6pt100

A license file is present.

Engineering

59

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (mupen64plus-video-gliden64/src/GLideNHQ/test).

CI/CD14pt100

CI is configured (.gitlab-ci.yml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (libretro/msvc/msvc-2013.sln).

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)
  • 144
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 395
    Watchers

Responsiveness

  • 5d 17h
    Median issue response
  • <1h
    Median PR merge time
  • 227
    Open issues
Repository files26 root entries
  • custom
  • docs
  • gles2n64
  • gles2rice
  • glide2gl
  • Graphics
  • include
  • jni
  • libretro
    Good: Dependency manifest found (libretro/msvc/msvc-2013.sln).
  • libretro-common
  • mupen64plus-core
  • mupen64plus-rsp-cxd4
  • mupen64plus-rsp-hle
  • mupen64plus-rsp-paraLLEl
    Good: A license file is present.
  • mupen64plus-video-angrylion
  • mupen64plus-video-gliden64
    Good: Test files detected (mupen64plus-video-gliden64/src/GLideNHQ/test).
  • mupen64plus-video-paraLLEl
  • scripts
    Good: Environment pinned via scripts/Dockerfile.
  • tools
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .gitmodules
  • Makefile
  • Makefile.common
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.