0
/ 100
Strong community interest, but docs and engineering haven't caught up to the hype.
Full Modular Monolith application with Domain-Driven Design approach.
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 (79).
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
82
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 MIT.
Engineering
57
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.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/buildPipeline.yml).
Test files detected (build/BuildIntegrationTests.cs).
.NET formatting configured (build/.editorconfig).
Project health
75
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Dependency manifest found (build/_build.csproj).
Repository has a description.
.gitignore present.
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/buildPipeline.yml).
- .nuke
- buildGood: Test files detected (build/BuildIntegrationTests.cs).Good: .NET formatting configured (build/.editorconfig).Good: Dependency manifest found (build/_build.csproj).
- docs
- src
- .gitignoreGood: .gitignore present.
- azure-pipelines.yml
- build.cmd
- build.ps1
- build.sh
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- LICENSEGood: Licensed under MIT.
- 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.
- runIntegrationTests.cmd
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kgrzybek/modular-monolith-with-ddd)