blurosie/hg-engine

0

/ 100

Documentation82
Engineering26
Health100
C3271d ago
Grade a repo

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

complete heart gold engine

Documentation

82

README12pt70

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

26

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

CI/CD14pt57

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

Reproducibility6pt80

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (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)
  • 293
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 35d 22h
    Median issue response
  • <1h
    Median PR merge time
  • 76
    Open issues
Repository files35 root entries
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • armips
  • asm
  • data
  • documentation
  • include
  • rawdata
  • scripts
  • sound
  • src
  • tools
    Good: A license file is present.
  • .clang-format
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • armhooks
  • bytereplacement
  • charmap.txt
  • CONFIG.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.
    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.
    Good: Contributing guide includes code examples.
  • CREDITS.md
  • docker-login.cmd
  • docker-makerom.cmd
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • dump.mk
  • hooks
  • Makefile
  • narcs.mk
  • overlays.mk
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README has code examples.
    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.
  • repoints
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • rom.ld
  • routinepointers