45
/ 100
The fundamentals need work — start with test coverage and CI.
Quick screenshot and annotation plugin for DankMaterialShell
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 (76).
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
69
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
24
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/auto-assign.yml).
Issue or PR templates present.
Project health
59
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
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)
- 5Forks
- 44Releaseslatest 1mo ago
Community
- 57% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 16Watchers
Responsiveness
- 5d 3hMedian issue response
- <1hMedian PR merge time
- 2Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/auto-assign.yml).Good: Issue or PR templates present.
- components
- dms-common
- docs
- scripts
- translations
- CaptureConfig.qml
- LICENSEGood: Licensed under MIT.
- plugin.json
- QuickCaptureDaemon.qml
- QuickCaptureModal.qml
- QuickCaptureSettings.qml
- QuickCaptureWidget.qml
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- screenshot.png
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/hthienloc/dms-quick-capture)