41
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
Windows, Android, and Linux ports of TLoZ: LADXHD updated via a patcher.
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 C (71).
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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
52
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
README is present.
README documents how to install the project.
Engineering
11
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
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 is configured (.github/workflows/build-launcher.yml).
Project health
100
Dependency manifest found (ladxhd_game_source_code/ProjectZ.Android/ProjectZ.Android.csproj).
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)
- 39Forks
- 87Releaseslatest 11mo ago
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 860Watchers
Responsiveness
- 3hMedian issue response
- 2hMedian PR merge time
- 19Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/build-launcher.yml).
- assets_original
- assets_patches
- icon
- ladxhd_game_source_codeGood: Dependency manifest found (ladxhd_game_source_code/ProjectZ.Android/ProjectZ.Android.csproj).
- ladxhd_launcher_source_code
- ladxhd_migrate_source_code
- ladxhd_patcher_source_code
- migration_tool_builds
- shared
- vcdiff_source_code
- .gitattributes
- .gitignoreGood: .gitignore present.
- CHANGELOG.md
- Directory.Build.props
- LADXHD-Migrater.exe
- LINUX.md
- MACOS.md
- MANUAL.md
- README.mdGood: 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.
- Unblock-All-Files.ps1
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/bigheadsmz/zelda-la-dx-hd-updated)