0

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Reverse engineering tool for linux games

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

42

Tests18pt0

No tests detected anywhere in the repository.

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

CI/CD14pt40

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

Reproducibility6pt70

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

Linting and formatting5pt100

Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (pyproject.toml).

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)
  • 182
    Forks
  • 7
    Releaseslatest 2d ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,992
    Watchers

Responsiveness

  • 2d 4h
    Median issue response
  • 2d 6h
    Median PR merge time
  • 9
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/build_docs.yml).
    Good: Issue or PR templates present.
  • .vscode
  • ci
  • docs
  • GUI
  • i18n
  • libpince
  • media
  • mono_collector
  • tr
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • AUTHORS
  • compile_ts.sh
  • 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.
    Good: Contributing guide describes code style expectations.
    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.
  • COPYING
  • COPYING.CC-BY
  • fix_ts.py
  • install.sh
  • libmemscan
  • PINCE.py
  • PINCE.sh
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • THANKS