REPOGEO REPORT · LITE

goharbor/harbor-helm

Default branch main · commit 7233a81d · scanned 6/23/2026, 12:07:38 PM

GitHub: 1,495 stars · 855 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

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

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 goharbor/harbor-helm, 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
Clarify README H1 to emphasize deploying a private container registry
Why:
CURRENT
```
# Helm Chart for Harbor
```
COPY-PASTE FIX
```
# Helm Chart for Harbor: Deploy a Private Container Registry on Kubernetes
```

hightopics#2

Add relevant topics for discoverability

Why:

COPY-PASTE FIX

helm, harbor, kubernetes, container-registry, docker-registry, private-registry, image-registry, devops, cloud-native

mediumhomepage#3
Add a homepage URL
Why:
COPY-PASTE FIX
```
https://goharbor.io
```

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 goharbor/harbor-helm

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

Nexus Repository Manager

Recommended in 2 of 2 queries

COMPETITOR LEADERBOARD

Nexus Repository Manager · recommended 2×
Artifactory · recommended 2×
GitLab Container Registry · recommended 2×
Harbor · recommended 1×
Registry · recommended 1×

CATEGORY QUERY
How to deploy a private Docker image registry within my Kubernetes cluster?
you: not recommended
AI recommended (in order):
1. Harbor
2. Registry
3. Nexus Repository Manager
4. Artifactory
5. GitLab Container Registry
AI recommended 5 alternatives but never named goharbor/harbor-helm. This is the gap to close.
Show full AI answer
CATEGORY QUERY
Kubernetes package manager for deploying a secure private container image repository?
you: not recommended
AI recommended (in order):
1. Harbor (goharbor/harbor)
2. Quay Enterprise
3. GitLab Container Registry
4. Nexus Repository Manager
5. Artifactory
AI recommended 5 alternatives but never named goharbor/harbor-helm. 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 goharbor/harbor-helm?
pass
AI named goharbor/harbor-helm explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts goharbor/harbor-helm in production, what risks or prerequisites should they evaluate first?
pass
AI named goharbor/harbor-helm 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 goharbor/harbor-helm solve, and who is the primary audience?
pass
AI named goharbor/harbor-helm 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 goharbor/harbor-helm. 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/goharbor/harbor-helm.svg)](https://repogeo.com/en/r/goharbor/harbor-helm)

HTML

<a href="https://repogeo.com/en/r/goharbor/harbor-helm"><img src="https://repogeo.com/badge/goharbor/harbor-helm.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

goharbor/harbor-helm — 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