0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Documentation
40
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
64
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
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.
Test files detected (tests).
CI is configured (.github/workflows/check-overdraft.yml).
.NET formatting configured (.editorconfig).
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (src/Meziantou.Moneiz.Cli/Meziantou.Moneiz.Cli.csproj).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 4Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 20Watchers
Responsiveness
- 3hMedian issue response
- 2hMedian PR merge time
- 1Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/check-overdraft.yml).
- doc
- img
- srcGood: Dependency manifest found (src/Meziantou.Moneiz.Cli/Meziantou.Moneiz.Cli.csproj).
- testsGood: Test files detected (tests).
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CLAUDE.md
- CODEOWNERS
- 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.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- Directory.Build.props
- Directory.Packages.props
- global.json
- LICENSE.txtGood: Licensed under MIT.
- Meziantou.Moneiz.slnx
- NuGet.Config
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- renovate.json