41
/ 100
Some interest. A stronger README and CI would help.
State-of-the-art feature-rich email client that supports many protocols
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 D (66).
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.
- 2README12pt
Add a README.md describing what the project does, how to install it, and how to run it.
- 3Install and run instructions9pt
Add a section showing how to install dependencies.
- 4Install and run instructions9pt
Add a section showing how to start or use the project.
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
0
No README found in the repository.
→ Add a README.md describing what the project does, how to install it, and how to run it.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
58
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.
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 (agents/mailfilteragent/tests).
CI is configured (.gitlab-ci.yml).
Project health
68
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.
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 26 / 97Commits (30d / 90d)
- 21Forks
- 0Releases
Community
- 12% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 86Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files31 root entries
- agentsGood: Test files detected (agents/mailfilteragent/tests).
- doc
- kmail-refresh-settings
- ktnef
- LICENSES
- po
- src
- .clang-format-pre-commit
- .codespellrc
- .craft.ini
- .gersemirc
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .gitlab-ci.ymlGood: CI is configured (.gitlab-ci.yml).
- .kde-ci.yml
- .pre-commit-config.yaml
- ClangBuildAnalyzer.ini
- CMakeLists.txt
- CMakePresets.json
- CMakePresets.json.license
- config-kmail.h.in
- cppcheck-suppressions.xml
- kmail-version.h.in
- logo.png
- MAINTAINERS
- readme-build-ftime.txtIssue: 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.
- README-pre-commit.md
- README-pre-commit.md.license
- REUSE.toml
- sanitizers.supp
- snapcraft.yaml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kde/kmail)