80

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

Top 32% of 5,156 graded repos

An unofficial rules engine for the world's greatest card game.

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

74

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt67

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

76

Reproducibility6pt0

No dependency lockfile found (−70 pts).

Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Tests18pt80

Test files detected (forge-game/src/test).

CI/CD14pt85

CI is configured (.github/workflows/test-android-build.yml).

Linting and formatting5pt100

Java/Kotlin linting configured (.checkstyle).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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

  • 305 / 924
    Commits (30d / 90d)
  • 973
    Forks
  • 27
    Releaseslatest 2y ago

Community

  • 75% - Good
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 2,466
    Watchers

Responsiveness

  • 4d
    Median issue response
  • 15h
    Median PR merge time
  • 574
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/test-android-build.yml).
    Good: Issue or PR templates present.
  • .mvn
  • adventure-editor
  • docs
  • forge-ai
  • forge-core
  • forge-game
    Good: 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
  • .checkstyle
    Good: Java/Kotlin linting configured (.checkstyle).
  • .fbprefs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AppIcon.png
  • checkstyle.xml
  • 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.
    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.
  • LICENSE
    Good: Licensed under GPL-3.0.
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • README.md
    Good: 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.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/card-forge/forge)](https://www.repo-grade.com/report/card-forge/forge)

More graded Java repos