0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A modded Slay the Spire experience on Android.
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
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 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
72
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under Other.
Engineering
51
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.
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/deploy-presence-pages.yml).
Test files detected (agent-connector/src/test).
Lockfile present (cloud-function/package-lock.json). Installs are reproducible.
Project health
100
Dependency manifest found (build.gradle.kts).
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)
- 7Forks
- 66Releaseslatest 5mo ago
Community
- -Community health
- -authors own >50% of commits
- 262Watchers
Responsiveness
- <1hMedian issue response
- -Median PR merge time
- 4Open issues
Repository files30 root entries
- .githubGood: CI is configured (.github/workflows/deploy-presence-pages.yml).
- .opencode
- agent-connectorGood: Test files detected (agent-connector/src/test).
- app
- boot-bridge
- cloud-functionGood: Lockfile present (cloud-function/package-lock.json). Installs are reproducible.
- cloudflare-presence-worker
- docs
- gradle
- macrobenchmark
- mods
- patches
- presence-service
- scripts
- steam-protocol
- tools
- workshop-core
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- docker-compose.yamlGood: Environment pinned via docker-compose.yaml.
- gradle.properties
- gradlew
- gradlew.bat
- NOTICE
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- settings.gradle.kts
- test.md
- THIRD_PARTY_LICENSES.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/modinmobilests/slaytheamethystmodded)