0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Minecraft 1.8.9 forge hacked client based on LiquidBounce.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 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
56
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under GPL-3.0.
Engineering
71
No Java/Kotlin linter configured.
→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.
CI is configured (.github/workflows/build.yml).
Test files detected (src/main/java/net/ccbluex/liquidbounce/features/module/modules/movement/longjumpmodes/ncp/NCPLatest.kt).
Lockfile present (nextgen-theme/package-lock.json). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (build.gradle).
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)
- 198Forks
- 35Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 504Watchers
Responsiveness
- 4hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot configured for gradle.Good: Issue or PR templates present.
- docs
- gradle
- libs
- nextgen-themeGood: Lockfile present (nextgen-theme/package-lock.json). Installs are reproducible.
- srcGood: Test files detected (src/main/java/net/ccbluex/liquidbounce/features/module/modules/movement/longjumpmodes/ncp/NCPLatest.kt).
- .gitignoreGood: .gitignore present.
- build.gradleGood: Dependency manifest found (build.gradle).
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under GPL-3.0.
- 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.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- settings.gradle
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/skiddermc/fdpclient)