0
/ 100
Strong community interest, but tests, CI, or docs need work.
This project aims to fix or address some issues in Grand Theft Auto IV: The Complete Edition
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (83).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under GPL-3.0.
Engineering
31
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/msvc_x86.yml).
Issue or PR templates present.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 109Forks
- 73Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 2,883Watchers
Responsiveness
- 6hMedian issue response
- 2hMedian PR merge time
- 54Open issues
Repository files23 root entries
- .githubGood: CI is configured (.github/workflows/msvc_x86.yml).Good: Dependabot covers 2 ecosystems (github-actions, gitsubmodule). Dependencies stay current.Good: Issue or PR templates present.
- data
- external
- installer
- shaders
- sourceGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- text
- textures
- tools
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- buildgxt.bat
- buildimg.bat
- buildshaders.bat
- buildwtd.bat
- licenseGood: Licensed under GPL-3.0.
- premake5.bat
- premake5.exe
- premake5.lua
- readme.mdGood: 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.
- release.bat
- sign.ps1
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/thirteenag/gtaiv.eflc.fusionfix)