RRepoGEO

REPOGEO REPORT · LITE

yoheimuta/protolint

Default branch master · commit ad17756f · scanned 6/13/2026, 2:11:51 PM

GitHub: 696 stars · 62 forks

AI VISIBILITY SCORE
66 /100
Needs work
Category recall
1 / 2
Avg rank #2.0 when recommended
Rule findings
1 pass · 1 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 yoheimuta/protolint, 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
    Emphasize automatic fixing for Go projects in the README's opening

    Why:

    CURRENT
    protolint is the pluggable linting/fixing utility for Protocol Buffer files (proto2+proto3):
    COPY-PASTE FIX
    protolint is the pluggable linting/fixing utility for Protocol Buffer files (proto2+proto3). It offers *automatic fixing* of style violations, making it an ideal tool for Go projects.
  • mediumhomepage#2
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    https://github.com/yoheimuta/protolint
  • lowtopics#3
    Add 'mcp' and 'model-context-protocol' to repository topics

    Why:

    CURRENT
    cli, fixer, golang, lint, linter, plugin-architecture, proto3, protobuf, protocol-buffers, style-linter
    COPY-PASTE FIX
    cli, fixer, golang, lint, linter, plugin-architecture, proto3, protobuf, protocol-buffers, style-linter, mcp, model-context-protocol

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
1 / 2
50% of queries surface yoheimuta/protolint
Avg rank
#2.0
Lower is better. #1 = top recommendation.
Share of voice
11%
Of all named tools, what % are you?
Top rival
bufbuild/buf
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. bufbuild/buf · recommended 1×
  2. golang/protobuf/protoc-gen-lint · recommended 1×
  3. googleapis/api-linter · recommended 1×
  4. zxh404/vscode-proto3 · recommended 1×
  5. Buf CLI · recommended 1×
  • CATEGORY QUERY
    What's a good linter for enforcing Protocol Buffer style guidelines and conventions?
    you: #2
    AI recommended (in order):
    1. Buf CLI (bufbuild/buf)
    2. protolint (yoheimuta/protolint) ← you
    3. protoc-gen-lint (golang/protobuf/protoc-gen-lint)
    4. Google's API Linter (googleapis/api-linter)
    5. vscode-proto3 (zxh404/vscode-proto3)
    Show full AI answer
  • CATEGORY QUERY
    How to automatically fix Protocol Buffer style violations in my Go project?
    you: not recommended
    AI recommended (in order):
    1. Buf CLI
    2. gofmt
    3. clang-format
    4. proto-gen-go-json

    AI recommended 4 alternatives but never named yoheimuta/protolint. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    warn

    Suggestion:

  • 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 yoheimuta/protolint?
    pass
    AI named yoheimuta/protolint explicitly

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

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

Subscribe to Pro for deep diagnoses

yoheimuta/protolint — 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