kde/plasma-workspace

0

/ 100

Documentation28
Engineering58
Health68
C++274today
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Various components needed to run a Plasma-based environment

Documentation

28

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt0

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.

README12pt25

README is present.

License6pt100

A license file is present.

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/applets/mediacontrollertest/test_1_basic_playback.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

  • 104 / 252
    Commits (30d / 90d)
  • 117
    Forks
  • 0
    Releases

Community

  • 25% - Weak
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 274
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files67 root entries
  • .gitlab
  • .reuse
  • appiumtests
    Good: Test files detected (appiumtests/applets/mediacontrollertest/test_1_basic_playback.py).
  • applets
  • appmenu
  • cmake
  • completions
  • components
  • containmentactions
  • devicenotifications
  • doc
  • donationmessage
  • freespacenotifier
  • geotimezoned
  • gmenu-dbusmenu-proxy
  • interactiveconsole
  • kcms
  • kioworkers
  • klipper
  • krunner
  • ksecretprompter
  • ksmserver
    Good: A license file is present.
  • ksplash
  • ktimezoned
  • libclock
  • libdbusmenuqt
  • libklookandfeel
  • libkmpris
  • libkworkspace
  • libnotificationmanager
  • libtaskmanager
  • LICENSES
  • login-sessions
  • logout-greeter
  • lookandfeel
  • menu
  • oom_notifier
  • plasma-windowed
  • plasmacalendarintegration
  • po
  • portal-configuration
  • runners
  • sddm-wayland-session
  • shell
  • solidautoeject
  • soliduiserver
  • startkde
  • statusnotifierwatcher
  • themes
  • wallpapers
  • xembed-sni-proxy
  • .contextProperties.ini
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .kde-ci.yml
  • c_ptr.h
  • CMakeLists.txt
  • config-appstream.h.cmake
  • config-KDECI_BUILD.h.cmake
  • config-workspace.h.cmake
  • config-X11.h.cmake
  • ConfigureChecks.cmake
  • ExtraDesktop.sh
  • HACKING
  • metainfo.yaml
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.