0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Multiplatform Music Player
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.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
53
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/github_workflows_build-release-apks_Version3.yml).
Test files detected (extensions/ayp/src/test).
Issue or PR templates present.
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)
- 25Forks
- 35Releaseslatest 6mo ago
Community
- -Community health
- -authors own >50% of commits
- 325Watchers
Responsiveness
- 1d 4hMedian issue response
- 3hMedian PR merge time
- 31Open issues
Repository files36 root entries
- .githubGood: CI is configured (.github/workflows/github_workflows_build-release-apks_Version3.yml).Good: Issue or PR templates present.
- .kotlin
- androidApp
- assets
- composeApp
- customVersion
- desktopDistribution
- docs
- extensionsGood: Test files detected (extensions/ayp/src/test).
- fastlane
- gradle
- updatedVersion
- .gitignoreGood: .gitignore present.
- .gitlab-ci.yml
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- bundletool.jar
- chart.svg
- createapks.cmd
- createDesktopDistributable.cmd
- createDesktopPackageDeb.cmd
- createDesktopPackageMsi.cmd
- createDesktopPackageRpm.cmd
- createtag.cmd
- crowdin.yml
- deletetag.cmd
- download-card.svg
- extractSigningKey.cmd
- gradle.properties
- gradlew
- gradlew.bat
- history.json
- LICENSEGood: Licensed under GPL-3.0.
- 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.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.
- settings.gradle.kts
- StartAA.bat
- stopGradleDaemon.cmd
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/fast4x/riplay)