kde/plasma-desktop

0

/ 100

Documentation56
Engineering58
Health68
QML1,273Other4d ago
Grade a repo

Strong community interest, but tests, CI, or docs need work.

Plasma for the Desktop

Documentation

56

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt55

README is present.

License6pt100

Licensed under Other.

Engineering

58

Linting and formatting5pt0

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Issue and PR templates6pt0

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.

Tests18pt80

Test files detected (appiumtests/kcms/kcm_kded_test.py).

CI/CD14pt100

CI is configured (.gitlab-ci.yml).

Project health

68

Dependency manifest6pt0

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 metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 63 / 121
    Commits (30d / 90d)
  • 147
    Forks
  • 0
    Releases

Community

  • 37% - Weak
    Community health
  • 7 bus factor
    authors own >50% of commits
  • 1,273
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files39 root entries
  • .reuse
  • .well-known
  • appiumtests
    Good: Test files detected (appiumtests/kcms/kcm_kded_test.py).
  • applets
  • attica-kde
  • cmake
  • containments
  • design
  • desktoppackage
  • doc
  • emojier
  • imports
  • kaccess
  • kcms
  • kconf_update
  • knetattach
  • layout-templates
  • LICENSES
  • po
  • runners
  • sddm-theme
  • solid-device-automounter
  • toolboxes
  • .contextProperties.ini
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .kde-ci.yml
  • CMakeLists.txt
  • CODEMAP.md
  • config-workspace.h.cmake
  • config-X11.h.cmake
  • ConfigureChecks.cmake
  • COPYING.DOC
  • kde-mimeapps.list
  • logo.png
  • Mainpage.dox
  • org.kde.plasmashell.metainfo.xml
  • README.md
    Good: 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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.