0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
A minimalist android launcher to help you quit your phone addiction
Documentation
81
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Other.
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/F-DroidCheck.yml).
Test files detected (core/common/src/androidTest/java/com/geecee/escapelauncher/core/common/ExampleInstrumentedTest.kt).
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)
- 33Forks
- 16Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 366Watchers
Responsiveness
- 12hMedian issue response
- 13hMedian PR merge time
- 36Open issues
Repository files27 root entries
- .agents
- .fdroid
- .githubGood: CI is configured (.github/workflows/F-DroidCheck.yml).Good: Issue or PR templates present.
- app
- branding
- build-logic
- coreGood: Test files detected (core/common/src/androidTest/java/com/geecee/escapelauncher/core/common/ExampleInstrumentedTest.kt).
- domain
- fastlane
- feature
- gradle
- .gitignoreGood: .gitignore present.
- .graphifyignore
- AGENTS.md
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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.
- google.gradle.kts
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under Other.
- proguard-rules.pro
- README.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- settings.gradle.kts
- STYLE_GUIDE.md