RRepoGEO

REPOGEO REPORT · LITE

qltysh/qlty

Default branch main · commit ddc59e77 · scanned 5/20/2026, 8:21:50 PM

GitHub: 3,062 stars · 265 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface qltysh/qlty, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Strengthen the README's main heading to clearly state the tool's identity

    Why:

    CURRENT
    ## Universal linting, auto-formatting, maintainability, and security scanning
    COPY-PASTE FIX
    ## Qlty: The Universal Code Quality CLI for Multi-Language Linting, Formatting, and Security Scanning
  • mediumreadme#2
    Add a clear statement about the project's license to the README

    Why:

    COPY-PASTE FIX
    ### 📄 License

Qlty is released under [specify license(s) here, e.g., 'a custom license combining X and Y']. Please refer to the [LICENSE file](LICENSE) for full details.
  • mediumcomparison#3
    Add a 'Comparison' or 'Why Qlty?' section to the README

    Why:

    COPY-PASTE FIX
    ### 🆚 Comparison / Why Qlty?

Qlty stands apart from single-language linters (like ShellCheck for shell scripts) by offering a unified, multi-language platform for over 70 static analysis tools across 40+ languages. Unlike individual linters, Qlty provides consistent configuration and reporting across your entire polyglot codebase, making it a comprehensive solution for teams managing diverse tech stacks. While tools like SonarQube offer similar breadth, Qlty focuses on a lightweight, CLI-first approach with easy integration into any CI/CD pipeline.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface qltysh/qlty
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
SonarSource/sonarqube
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. SonarSource/sonarqube · recommended 1×
  2. GitHub Actions · recommended 1×
  3. GitLab CI/CD · recommended 1×
  4. jenkinsci/jenkins · recommended 1×
  5. pre-commit/pre-commit · recommended 1×
  • CATEGORY QUERY
    How to enforce consistent code quality across multiple programming languages in a single project?
    you: not recommended
    AI recommended (in order):
    1. SonarQube (SonarSource/sonarqube)
    2. GitHub Actions
    3. GitLab CI/CD
    4. Jenkins (jenkinsci/jenkins)
    5. Pre-commit (pre-commit/pre-commit)
    6. Mega-Linter (megalinter/megalinter)
    7. Reviewdog (reviewdog/reviewdog)
    8. ESLint (eslint/eslint)
    9. Prettier (prettier/prettier)
    10. Black (psf/black)
    11. Flake8 (PyCQA/flake8)
    12. Pylint (PyCQA/pylint)
    13. gofmt
    14. golangci-lint (golangci/golangci-lint)
    15. Checkstyle (checkstyle/checkstyle)
    16. PMD (pmd/pmd)
    17. Google Java Format (google/google-java-format)
    18. Eclipse JDT
    19. Clang-Format
    20. Clang-Tidy
    21. StyleCop (StyleCop/StyleCop)
    22. dotnet format
    23. PHP_CodeSniffer (squizlabs/PHP_CodeSniffer)
    24. PHP-CS-Fixer (PHP-CS-Fixer/PHP-CS-Fixer)
    25. RuboCop (rubocop/rubocop)
    26. EditorConfig

    AI recommended 26 alternatives but never named qltysh/qlty. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best tools for comprehensive static analysis, formatting, and security scanning in CI/CD?
    you: not recommended
    AI recommended (in order):
    1. SonarQube
    2. GitHub Advanced Security
    3. GitLab Ultimate
    4. CodeQL
    5. Dependabot
    6. Checkmarx CxSAST
    7. Snyk
    8. Black Duck by Synopsys
    9. Black
    10. ESLint
    11. Prettier
    12. Flake8
    13. Bandit

    AI recommended 13 alternatives but never named qltysh/qlty. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of qltysh/qlty?
    pass
    AI named qltysh/qlty explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts qltysh/qlty in production, what risks or prerequisites should they evaluate first?
    pass
    AI named qltysh/qlty explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo qltysh/qlty solve, and who is the primary audience?
    pass
    AI named qltysh/qlty explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of qltysh/qlty. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/qltysh/qlty.svg)](https://repogeo.com/en/r/qltysh/qlty)
HTML
<a href="https://repogeo.com/en/r/qltysh/qlty"><img src="https://repogeo.com/badge/qltysh/qlty.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

qltysh/qlty — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite