gcompris/gcompris-qt
Grade a repo

62

/ 100

GradeD

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

Higher than 46% of 5,156 graded repos

GCompris in Qt Quick - Mirror of https://invent.kde.org/education/gcompris

Documentation47
Engineering58
Health100
QML2541mo ago

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 (78).

See your top fixes
Now
D
62
Potential
C
78

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  3. 3
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  4. 4
    Install and run instructions9pt

    Add a section showing how to install dependencies.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

47

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.

README12pt75

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 (tests).

CI/CD14pt100

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (android/build.gradle).

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

  • -
    Commits (30d / 90d)
  • 178
    Forks
  • 0
    Releases

Community

  • 25% - Weak
    Community health
  • -
    authors own >50% of commits
  • 254
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 1d 8h
    Median PR merge time
  • 12
    Open issues
Repository files35 root entries
  • android
    Good: Dependency manifest found (android/build.gradle).
  • cmake
  • docs
  • external
  • fastlane
  • images
  • installer
  • LICENSES
  • platforms
  • po
  • poqm
  • src
    Good: A license file is present.
  • tests
    Good: Test files detected (tests).
  • tools
  • .clang-format
  • .flatpak-manifest-teachers.json
  • .flatpak-manifest.json
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .gitmodules
  • .kde-ci.yml
  • CMakeLists.txt
  • cppcheck-suppressions.xml
  • HACKING
  • logo.png
  • org.kde.gcompris-teachers.appdata.xml
  • org.kde.gcompris-teachers.desktop
  • org.kde.gcompris.appdata.xml
  • org.kde.gcompris.desktop
  • publiccode.yml
  • README
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • README.md
  • REUSE.toml
  • snapcraft.yaml
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/gcompris/gcompris-qt)](https://www.repo-grade.com/report/gcompris/gcompris-qt)

More graded QML repos