0
/ 100
Strong community interest, but tests, CI, or docs need work.
Android Easter Egg Collections
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 A (92).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
40
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/crowdin.yml).
Lockfile present (Gemfile.lock). Installs are reproducible.
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (Gemfile).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 77Forks
- 59Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 1,221Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 10Open issues
Repository files36 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: CI is configured (.github/workflows/crowdin.yml).Good: Dependabot covers 3 ecosystems (gradle, github-actions, pip). Dependencies stay current.Good: Issue or PR templates present.
- .ideaIssue: Build artifacts or local files may be committed (.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
- .opencode
- app
- assets
- basic
- build-logic
- core
- eggs
- fastlane
- feature
- gradle
- jvm-basic
- script
- .gitignoreGood: .gitignore present.
- .gitmodules
- .issuetracker
- AGENTS.md
- build.gradle.kts
- BUILD.md
- CHANGELOG_zh.md
- CHANGELOG.md
- crowdin.yml
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under Apache-2.0.
- README_ja.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.Good: README documents how to install the project.Good: README documents how to run the project.
- README_zh.md
- README.md
- SECURITY.mdGood: Security policy present.
- settings.gradle.kts
- TODO.md
- wiki
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/hushenghao/androideastereggs)