0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
A smart project structure
Top 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
93
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
68
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.
CI is configured (.github/workflows/ci.yml).
Test files detected (example/ios/RunnerTests/RunnerTests.swift).
Lockfile present (doc/yarn.lock). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (doc/package.json).
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)
- 275Forks
- 14Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 1,380Watchers
Responsiveness
- 8hMedian issue response
- 5hMedian PR merge time
- 0Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- art
- docGood: Lockfile present (doc/yarn.lock). Installs are reproducible.Good: Environment pinned via doc/Dockerfile.Good: Dependency manifest found (doc/package.json).
- exampleGood: Test files detected (example/ios/RunnerTests/RunnerTests.swift).
- lib
- test
- tool
- .all-contributorsrc
- .gitignoreGood: .gitignore present.
- .metadata
- .pubignore
- analysis_options.yaml
- CHANGELOG.md
- CLAUDE.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.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.Good: Contributing guide includes code examples.
- devtools_options.yaml
- flutter_modular.png
- LICENSEGood: Licensed under Other.
- 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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/flutterando/modular)