0
/ 100
Strong community interest, but tests, CI, or docs need work.
A Windows context menu management tool with new menu monitoring
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 (82).
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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
78
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 is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
24
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/manual-release.yml).
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (ContextMenuMgr.Backend/ContextMenuMgr.Backend.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 36Forks
- 30Releaseslatest 3mo ago
Community
- -Community health
- -authors own >50% of commits
- 2,672Watchers
Responsiveness
- <1hMedian issue response
- 10hMedian PR merge time
- 17Open issues
Repository files22 root entries
- .githubGood: CI is configured (.github/workflows/manual-release.yml).Good: Issue or PR templates present.
- .ideaIssue: Build artifacts or local files may be committed (.idea/.idea.ContextMenuMgr) (−40 pts).Fix: Remove them and add to .gitignore.
- ContextMenuMgr.BackendGood: Dependency manifest found (ContextMenuMgr.Backend/ContextMenuMgr.Backend.csproj).
- ContextMenuMgr.Contracts
- ContextMenuMgr.Frontend
- ContextMenuMgr.ProbeHost
- ContextMenuMgr.TrayHost
- docs
- InstallerGood: Licensed under GPL-3.0.
- Scripts
- .gitignoreGood: .gitignore present.
- .gitmodules
- AGENTS.md
- build-beta.bat
- build-release.bat
- build.ps1
- CLAUDE.md
- ContextMenuMgr.slnx
- LICENSE
- NuGet.Config
- README.en.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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- README.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/plfjy/contextmenumgr)