62
/ 100
Strong community interest, but tests, CI, or docs need work.
Every day is worth remembering...
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 C (73).
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 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
63
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 documents how to install the project.
README is present.
Licensed under GPL-3.0.
Engineering
46
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.
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.
CI is configured (.github/workflows/fastlane.yml).
Test files detected (ios/RunnerTests/RunnerTests.swift).
Project health
100
Dependency manifest found (android/app/build.gradle).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 44 / 165Commits (30d / 90d)
- 44Forks
- 70Releaseslatest 2y ago
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 1,173Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 63Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/fastlane.yml).
- .vscode
- androidGood: Dependency manifest found (android/app/build.gradle).
- assets
- fastlane
- iosGood: Test files detected (ios/RunnerTests/RunnerTests.swift).
- lib
- linux
- macos
- snap
- submodules
- windows
- .envrc
- .gitignoreGood: .gitignore present.
- .gitmodules
- .metadata
- analysis_options.yaml
- AppImageBuilder.yml
- build_release.sh
- flake.lock
- flake.nix
- l10n.yaml
- LICENSE.txtGood: Licensed under GPL-3.0.
- prepare_release.sh
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/demizo/daily_you)