65
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Syntax highlighting Engine for Structured Text and Code.
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 (73).
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 GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
52
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.
README is present.
README documents how to install the project.
Engineering
59
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 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).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
Test files detected (autotests/input/test.kt).
CI is configured (.gitlab-ci.yml).
Project health
100
Dependency manifest found (autotests/input/build.gradle).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 71Forks
- 0Releases
Community
- 25% - WeakCommunity health
- 3 bus factorauthors own >50% of commits
- 169Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files18 root entries
- autotestsGood: Test files detected (autotests/input/test.kt).Good: Environment pinned via autotests/input/Dockerfile.Good: Dependency manifest found (autotests/input/build.gradle).
- data
- examples
- LICENSES
- poqm
- src
- utils
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .gitlab-ci.ymlGood: CI is configured (.gitlab-ci.yml).
- .kateconfig
- .kde-ci.yml
- .krazy
- .yamlignore
- CMakeLists.txt
- KF6SyntaxHighlightingConfig.cmake.in
- metainfo.yaml
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kde/syntax-highlighting)