62
/ 100
A workable base with real gaps. Start with test coverage and CI.
Visualize your growth.
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 (88).
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
88
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
31
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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/build-apk.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (android/app/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
- 116 / 677Commits (30d / 90d)
- 4Forks
- 10Releaseslatest 14d ago
Community
- 71% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 98Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 3Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/build-apk.yml).Good: Dependabot covers 3 ecosystems (pub, gradle, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- androidGood: Dependency manifest found (android/app/build.gradle.kts).
- assets
- fastlane
- lib
- web
- .flutter-version
- .gitignoreGood: .gitignore present.
- analysis_options.yaml
- CHANGELOG.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Good: Contributing guide describes code style expectations.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.Good: Contributing guide includes code examples.
- Grove_backup_DEMO.json
- l10n.yaml
- LICENSEGood: Licensed under GPL-3.0.
- pubspec.lock
- pubspec.yaml
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/resurrectdev1/grove)