RRepoGEO

REPOGEO REPORT · LITE

anjia0532/gcr.io_mirror

Default branch master · commit 669c0145 · scanned 6/25/2026, 8:48:04 PM

GitHub: 1,388 stars · 445 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
22 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
1 / 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 anjia0532/gcr.io_mirror, 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 README's opening to clarify its unique value proposition

    Why:

    CURRENT
    Google Container Registry Mirror(Google Container Registry镜像加速)
Disclaimer/免责声明
    COPY-PASTE FIX
    anjia0532/gcr.io_mirror provides a publicly accessible mirror for Google Container Registry (gcr.io), k8s.gcr.io, registry.k8s.io, quay.io, and ghcr.io images. It is specifically designed to help users in restricted network environments (e.g., mainland China) quickly pull essential container images for Kubernetes and other Docker-based applications, bypassing common access limitations.
  • mediumtopics#2
    Add more specific topics to improve categorization

    Why:

    CURRENT
    docker, gcr, k8s, kubectl, kubernetes
    COPY-PASTE FIX
    docker, gcr, k8s, kubectl, kubernetes, container-mirror, registry-mirror, restricted-network, china-mirror, image-proxy, container-registry
  • lowhomepage#3
    Add the repository URL as the homepage

    Why:

    COPY-PASTE FIX
    https://github.com/anjia0532/gcr.io_mirror

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 anjia0532/gcr.io_mirror
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Nexus Repository Manager
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Nexus Repository Manager · recommended 2×
  2. Artifactory · recommended 2×
  3. Harbor · recommended 1×
  4. Registry · recommended 1×
  5. Squid Proxy · recommended 1×
  • CATEGORY QUERY
    How can I speed up pulling Kubernetes core images in restricted network environments?
    you: not recommended
    AI recommended (in order):
    1. Harbor
    2. Nexus Repository Manager
    3. Artifactory
    4. Registry
    5. Squid Proxy
    6. Containerd

    AI recommended 6 alternatives but never named anjia0532/gcr.io_mirror. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are options for mirroring public container registries to improve pull performance?
    you: not recommended
    AI recommended (in order):
    1. Harbor (goharbor/harbor)
    2. Nexus Repository Manager
    3. Artifactory
    4. Azure Container Registry (ACR)
    5. Google Container Registry (GCR)
    6. Artifact Registry
    7. AWS Elastic Container Registry (ECR)

    AI recommended 7 alternatives but never named anjia0532/gcr.io_mirror. 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 anjia0532/gcr.io_mirror?
    pass
    AI did not name anjia0532/gcr.io_mirror — 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 anjia0532/gcr.io_mirror in production, what risks or prerequisites should they evaluate first?
    pass
    AI named anjia0532/gcr.io_mirror 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 anjia0532/gcr.io_mirror solve, and who is the primary audience?
    pass
    AI did not name anjia0532/gcr.io_mirror — 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 anjia0532/gcr.io_mirror. 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/anjia0532/gcr.io_mirror.svg)](https://repogeo.com/en/r/anjia0532/gcr.io_mirror)
HTML
<a href="https://repogeo.com/en/r/anjia0532/gcr.io_mirror"><img src="https://repogeo.com/badge/anjia0532/gcr.io_mirror.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

anjia0532/gcr.io_mirror — 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
anjia0532/gcr.io_mirror — RepoGEO report