Good shape overall. A few tweaks would push it into the top tier.

Desktop Planetarium

Documentation

74

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

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

CI/CD14pt100

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (kstars/python/setup.py).

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)
  • 132
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 275
    Watchers

Responsiveness

  • Median issue response
  • Median PR merge time
  • 0
    Open issues
Repository files49 root entries
  • .gitlab-ci
  • .lldb
  • .reuse
  • .vscode
  • appimage
  • cmake
  • datahandlers
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • examples
  • kstars
    Good: A license file is present.
    Good: Dependency manifest found (kstars/python/setup.py).
  • LICENSES
  • packaging
  • po
  • shared-modules
  • Tests
    Good: Test files detected (Tests).
  • tools
  • utils
  • .astyle-version
  • .astylerc
  • .craft.ini
  • .flatpak-manifest.json
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .kde-ci.yml
  • .krazy
  • AUTHORS
  • ChangeLog
  • CMakeLists.txt
  • config-kstars.h.cmake
  • INSTALL
  • logo.png
  • Mainpage.dox
  • metainfo.yaml
  • org.kde.kf5auth.kstars.actions
  • org.kde.kstars.appdata.xml
  • README.android
    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.
    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.
    Good: README documents how to run the project.
  • README.cicd
  • README.customize
  • README.ephemerides
  • README.i18n
  • README.images
  • README.md
  • README.planetmath
  • README.timekeeping
  • snapcraft.yaml
  • timekeeping.dox
  • TODO