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

Qualitative data analysis for text, images, audio, video. Cross platform. Python 3.12 or newer and PyQt6.

Documentation

90

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under LGPL-3.0.

Engineering

71

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.

Reproducibility6pt70

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt72

CI is configured (.github/workflows/python-app.yml).

Tests18pt80

Test files detected (tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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)
  • 131
    Forks
  • 23
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 5h
    Median issue response
  • <1h
    Median PR merge time
  • 22
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/python-app.yml).
    Good: Issue or PR templates present.
  • doc
  • Examples
  • icons
  • other_languages
  • src
  • tests
    Good: Test files detected (tests).
  • .gitignore
    Good: .gitignore present.
  • 2023QualCoder.code-workspace
  • CITATION.cff
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
  • install_fedora_DONT_USE_KEEPING_JUST_IN_CASE.sh
  • LICENSE.txt
    Good: Licensed under LGPL-3.0.
  • mac_build-dmg.sh
  • MANIFEST.in
  • QC_Logo.ico
  • qualcoder_onefile.spec
  • qualcoder.png
  • qualcoder.spec
  • 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.
    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.
  • rebuild_lang.py
  • rebuild_ui.py
  • Release_notes.md
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • ROADMAP.md
  • run_from_source_Ubuntu.sh
  • run_from_source_Windows.bat