80
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
An unofficial rules engine for the world's greatest card game.
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 a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
74
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under GPL-3.0.
Engineering
76
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
Test files detected (forge-game/src/test).
CI is configured (.github/workflows/test-android-build.yml).
Java/Kotlin linting configured (.checkstyle).
Issue or PR templates present.
Project health
100
Dependency manifest found (pom.xml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 305 / 924Commits (30d / 90d)
- 973Forks
- 27Releaseslatest 2y ago
Community
- 75% - GoodCommunity health
- 4 bus factorauthors own >50% of commits
- 2,466Watchers
Responsiveness
- 4dMedian issue response
- 15hMedian PR merge time
- 574Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/test-android-build.yml).Good: Issue or PR templates present.
- .mvn
- adventure-editor
- docs
- forge-ai
- forge-core
- forge-gameGood: Test files detected (forge-game/src/test).
- forge-gui
- forge-gui-android
- forge-gui-desktop
- forge-gui-ios
- forge-gui-mobile
- forge-gui-mobile-dev
- forge-installer
- forge-lda
- .checkstyleGood: Java/Kotlin linting configured (.checkstyle).
- .fbprefs
- .gitattributes
- .gitignoreGood: .gitignore present.
- AppIcon.png
- checkstyle.xml
- CONTRIBUTING.mdGood: 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.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSEGood: Licensed under GPL-3.0.
- pom.xmlGood: Dependency manifest found (pom.xml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.Good: README includes status badges.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/card-forge/forge)