80
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Mirror of 2009scape GitLab so I can get some nice little green boxes on my profile. For bug reports and pull requests please use the offical Gitlab repo below.
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.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Reproducibility6pt
Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated 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
85
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 is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
69
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.
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 (Server/src/main/content/region/kandarin/quest/fishingcontest/FishingContest.java).
CI is configured (.gitlab-ci.yml).
Java/Kotlin linting configured (Server/detekt.yml).
Project health
100
Dependency manifest found (Server/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
- -Commits (30d / 90d)
- 4Forks
- 0Releases
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 14Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files18 root entries
- .gitlab
- dumps
- Proto
- ServerGood: Test files detected (Server/src/main/content/region/kandarin/quest/fishingcontest/FishingContest.java).Good: Java/Kotlin linting configured (Server/detekt.yml).Good: Dependency manifest found (Server/pom.xml).
- Tools
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitlab-ci.ymlGood: CI is configured (.gitlab-ci.yml).
- build
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under AGPL-3.0.
- make-release.py
- mysql.env.example
- 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.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.
- run
- run-server.bat
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/downthecrop/2009scape-mirror)