RRepoGEO

REPOGEO REPORT · LITE

repowise-dev/repowise

Default branch main · commit 69d5a908 · scanned 6/18/2026, 3:08:06 AM

GitHub: 2,425 stars · 311 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 repowise-dev/repowise, 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
    Reposition the README's opening paragraph to explicitly list its core functions

    Why:

    CURRENT
    <p align="center"><em>The codebase intelligence layer for the AI era. Context your AI agent can use, and the health, risk, and ownership signals your team can trust.</em></p>
    COPY-PASTE FIX
    <p align="center"><em>Repowise provides codebase intelligence for AI-assisted engineering teams, offering code health scores, auto-generated documentation, git analytics, dead code detection, and architectural decision support via MCP.</em></p>
  • mediumreadme#2
    Add a concise 'How Repowise Compares' section to the README

    Why:

    COPY-PASTE FIX
    ## How Repowise Compares

Repowise offers a unique codebase intelligence layer for AI-assisted engineering, integrating code health, git analytics, and architectural insights with a focus on providing context for AI agents. This goes beyond the scope of traditional static analysis tools like SonarQube or DeepSource, offering a holistic, multi-repo view. [See a detailed comparison here.](#how-it-compares)
  • mediumreadme#3
    Clarify the project's license(s) directly in the README

    Why:

    COPY-PASTE FIX
    ## License

Repowise is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). Please see the [LICENSE](LICENSE) file for full details.

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 repowise-dev/repowise
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
SonarQube
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. SonarQube · recommended 2×
  2. DeepSource · recommended 1×
  3. Pylint · recommended 1×
  4. Bandit · recommended 1×
  5. CodeClimate · recommended 1×
  • CATEGORY QUERY
    What tools help analyze codebase health, detect dead code, and assist AI engineering teams?
    you: not recommended
    AI recommended (in order):
    1. SonarQube
    2. DeepSource
    3. Pylint
    4. Bandit
    5. CodeClimate
    6. Snyk
    7. Radon

    AI recommended 7 alternatives but never named repowise-dev/repowise. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a solution for automated code documentation, git analytics, and architectural insights.
    you: not recommended
    AI recommended (in order):
    1. Understand.dev
    2. CodeScene
    3. Sourcegraph
    4. DocFX
    5. SonarQube
    6. GitKraken
    7. GitLens

    AI recommended 7 alternatives but never named repowise-dev/repowise. 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 repowise-dev/repowise?
    pass
    AI named repowise-dev/repowise explicitly

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

  • If a team adopts repowise-dev/repowise in production, what risks or prerequisites should they evaluate first?
    pass
    AI named repowise-dev/repowise 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 repowise-dev/repowise solve, and who is the primary audience?
    pass
    AI named repowise-dev/repowise 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 repowise-dev/repowise. 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/repowise-dev/repowise.svg)](https://repogeo.com/en/r/repowise-dev/repowise)
HTML
<a href="https://repogeo.com/en/r/repowise-dev/repowise"><img src="https://repogeo.com/badge/repowise-dev/repowise.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

repowise-dev/repowise — 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