Good community traction and solid fundamentals. Nearly in the top tier.

A simplified touch optimized interface for QGIS

Documentation

79

Install and run instructions9pt45

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

Add a section showing how to install dependencies.

Contributing guide5pt66

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

License6pt100

Licensed under GPL-2.0.

Engineering

74

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.

CI/CD14pt72

CI is configured (.github/workflows/build_artifact_comment.yml).

Tests18pt80

Test files detected (test).

Reproducibility6pt100

Lockfile present (Gemfile.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

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)
  • 335
    Forks
  • 272
    Releaseslatest 9y ago

Community

  • Community health
  • authors own >50% of commits
  • 1,277
    Watchers

Responsiveness

  • 7d 17h
    Median issue response
  • 8h
    Median PR merge time
  • 194
    Open issues
Repository files36 root entries
  • .devcontainer
  • .docker
    Good: Environment pinned via .docker/android_dev/Dockerfile.
  • .github
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
    Good: CI is configured (.github/workflows/build_artifact_comment.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, bundler). Dependencies stay current.
    Good: Issue or PR templates present.
  • .tx
  • cmake
  • doc
  • docs
  • fastlane
  • i18n
  • images
  • platform
  • resources
  • scripts
  • src
  • test
    Good: Test files detected (test).
  • vcpkg
  • .clang-format
  • .cmake-format.yaml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .qmlformat.ini
  • .zenodo.json
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE
    Good: Licensed under GPL-2.0.
  • mkdocs.yml
  • publiccode.yml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    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.
  • RELEASE_NAME
  • release_names_history.md
  • SECURITY.md
    Good: Security policy present.
  • vcpkg.json