hailtododongo/pyrite64
Grade a repo

0

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

N64 Game-Engine and Editor using libdragon & tiny3d

Documentation72
Engineering77
Health100
C++3,160MITtoday

Documentation

72

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

77

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (docs/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (n64/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/requirements.txt).

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)
  • 135
    Forks
  • 8
    Releaseslatest 13d ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 3,160
    Watchers

Responsiveness

  • 11h
    Median issue response
  • 7h
    Median PR merge time
  • 22
    Open issues
Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/docs.yml).
    Good: Issue or PR templates present.
  • data
  • docs
    Good: Lockfile present (docs/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (docs/requirements.txt).
  • n64
    Good: Test files detected (n64/tests).
  • packaging
  • scripts
  • src
  • tools
  • vendored
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CMakeLists.txt
  • CMakePresets.json
  • LICENSE
    Good: Licensed under MIT.
  • Readme.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.