REPOGEO REPORT · LITE

gitkraken/vscode-gitlens

Default branch main · commit 1c668f3e · scanned 6/26/2026, 3:26:55 AM

GitHub: 9,846 stars · 1,743 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)

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

AI VISIBILITY SCORE

20 /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

0 / 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 gitkraken/vscode-gitlens, 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

highabout#1

Explicitly link "GitLens" product name to the `gitkraken/vscode-gitlens` repository in the description

Why:

CURRENT

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more

COPY-PASTE FIX

Supercharge Git inside VS Code with GitLens (gitkraken/vscode-gitlens), unlocking untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more.

mediumreadme#2

Clarify the existing license(s) in the README

Why:

COPY-PASTE FIX

Add a section or line in the README, e.g., "## License\nGitLens is licensed under [describe license(s) here, e.g., a custom license, or a combination of X and Y]. Please see the [LICENSE file](LICENSE) for full details."

lowtopics#3

Expand repository topics with more specific keywords

Why:

CURRENT

git, github, vscode, vscode-extension

COPY-PASTE FIX

git, github, vscode, vscode-extension, git-blame, codelens, code-history, code-review, git-visualization, git-explorer

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 gitkraken/vscode-gitlens

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

Git History

Recommended in 2 of 2 queries

COMPETITOR LEADERBOARD

Git History · recommended 2×
Git Graph · recommended 2×
GitLens · recommended 1×
Git Blame · recommended 1×
CodeStream · recommended 1×

CATEGORY QUERY
How can I visualize Git blame and code authorship directly within my VS Code editor?
you: not recommended
AI recommended (in order):
1. GitLens
2. Git Blame
3. CodeStream
4. Git History
5. Git Graph
AI recommended 5 alternatives but never named gitkraken/vscode-gitlens. This is the gap to close.
Show full AI answer
CATEGORY QUERY
What VS Code extensions help understand repository history and accelerate code reviews?
you: not recommended
AI recommended (in order):
1. GitLens — Git supercharged
2. Git History
3. GitHub Pull Requests and Issues
4. Git Graph
5. CodeStream: Collaboration for VS Code
6. Live Share
7. Partial Diff
AI recommended 7 alternatives but never named gitkraken/vscode-gitlens. 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 gitkraken/vscode-gitlens?
pass
AI did not name gitkraken/vscode-gitlens — likely talking about a different project
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts gitkraken/vscode-gitlens in production, what risks or prerequisites should they evaluate first?
pass
AI did not name gitkraken/vscode-gitlens — likely talking about a different project
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 gitkraken/vscode-gitlens solve, and who is the primary audience?
pass
AI did not name gitkraken/vscode-gitlens — likely talking about a different project
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 gitkraken/vscode-gitlens. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

Live preview

MARKDOWN (README)

[![RepoGEO](https://repogeo.com/badge/gitkraken/vscode-gitlens.svg)](https://repogeo.com/en/r/gitkraken/vscode-gitlens)

HTML

<a href="https://repogeo.com/en/r/gitkraken/vscode-gitlens"><img src="https://repogeo.com/badge/gitkraken/vscode-gitlens.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

gitkraken/vscode-gitlens — 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