Strong community interest, but tests, CI, or docs need work.
Multi-platform app that allows your devices to communicate
Documentation
46
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
README documents how to install the project.
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Engineering
68
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 (tests).
CI is configured (.gitlab-ci.yml).
Linter or formatter configured (.editorconfig).
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
- —Commits (30d / 90d)
- 258Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 3 bus factorauthors own >50% of commits
- 3,808Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files32 root entries
- .gitlab
- app
- cli
- cmake
- core
- daemon
- data
- dbusinterfaces
- declarativeplugin
- fileitemactionplugin
- icons
- indicator
- kio
- LICENSES
- models
- nautilus-extension
- plasmoid
- plugins
- po
- smsapp
- testsGood: Test files detected (tests).
- urlhandler
- .craft.ini
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .gitlab-ci.ymlGood: CI is configured (.gitlab-ci.yml).
- .kde-ci.yml
- CMakeLists.txt
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- KDEConnectMacros.cmake
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- REUSE.toml