kde/kdevelop

0

/ 100

Documentation56
Engineering59
Health62
C++585Other1d ago
Grade a repo

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

Cross-platform IDE for C, C++, Python, QML/JavaScript and PHP

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

59

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.

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (kdevplatform/debugger/tests).

CI/CD14pt100

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

Project health

62

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.

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 108
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 585
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files39 root entries
  • .reuse
  • 3rdparty
    Good: Licensed under Other.
  • app
  • app_templates
  • appimage
    Good: Environment pinned via appimage/Dockerfile.
  • cmake
  • developer-scripts
  • doc
  • file_templates
  • kdevplatform
    Good: Test files detected (kdevplatform/debugger/tests).
  • LICENSES
  • pics
  • plugins
    Issue: Build artifacts or local files may be committed (plugins/qmljs/tests/files/node_modules/module.js) (−40 pts).Fix: Remove them and add to .gitignore.
  • po
  • release-scripts
  • share
  • shortcuts
  • .clang-format
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .kateconfig
  • .kateproject
  • .kde-ci.yml
  • .krazy
  • AUTHORS
  • CMakeLists.txt
  • config-kdevelop.h.cmake
  • COPYING.DOC
  • Doxyfile
  • ExtraDesktop.sh
  • format_sources
  • format.config.uncrustify
  • INSTALL
  • kdevelop.kdev4
  • KDevelopConfig.cmake.in
  • org.kde.kdevelop.appdata.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.
  • snapcraft.yaml