REPOGEO REPORT · LITE

incidentfox/incidentfox

Default branch main · commit 1b6ffad4 · scanned 6/10/2026, 9:56:59 AM

GitHub: 619 stars · 71 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

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

2 / 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 incidentfox/incidentfox, 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

Strengthen README introduction to highlight AI as the core differentiator

Why:

CURRENT

**IncidentFox** is the open-source AI SRE that automatically investigates production incidents, correlates alerts, analyzes logs, and finds root causes.

COPY-PASTE FIX

**IncidentFox** is the only open-source AI SRE platform that autonomously investigates production incidents, correlates alerts, analyzes logs, and finds root causes, providing a powerful alternative to commercial AI incident management solutions.

mediumreadme#2

Add a dedicated comparison section to the README

Why:

COPY-PASTE FIX

Add a new section to the README, such as '## Why IncidentFox? (vs. Commercial Solutions)' or '## IncidentFox vs. PagerDuty, Splunk On-Call, etc.', detailing its unique advantages like open-source nature, self-hosting, specific AI capabilities, and cost-effectiveness.

lowreadme#3

Clarify the project's license(s) in the README

Why:

COPY-PASTE FIX

Add a new section to the README, e.g., '## License
IncidentFox is licensed under [Specific License Name(s) here]. Please refer to the [LICENSE file](LICENSE) for full details.' (Maintainer should replace '[Specific License Name(s) here]' with the actual license name(s) from the LICENSE file).

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

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

PagerDuty

Recommended in 2 of 2 queries

COMPETITOR LEADERBOARD

PagerDuty · recommended 2×
Splunk On-Call · recommended 2×
Grafana Incident · recommended 1×
Cortex · recommended 1×
Jira Service Management · recommended 1×

CATEGORY QUERY
How can I automate incident investigation and root cause analysis in my SRE workflow?
you: not recommended
AI recommended (in order):
1. PagerDuty
2. Splunk On-Call
3. Grafana Incident
4. Cortex
5. Jira Service Management
6. Gremlin
7. Lightstep
AI recommended 7 alternatives but never named incidentfox/incidentfox. This is the gap to close.
Show full AI answer
CATEGORY QUERY
What are the best AI-powered tools for incident management and SRE automation?
you: not recommended
AI recommended (in order):
1. PagerDuty
2. Splunk On-Call
3. Moogsoft
4. BigPanda
5. Dynatrace
6. Datadog
7. ServiceNow IT Operations Management (ITOM)
AI recommended 7 alternatives but never named incidentfox/incidentfox. 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 incidentfox/incidentfox?
pass
AI did not name incidentfox/incidentfox — 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 incidentfox/incidentfox in production, what risks or prerequisites should they evaluate first?
pass
AI named incidentfox/incidentfox 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 incidentfox/incidentfox solve, and who is the primary audience?
pass
AI named incidentfox/incidentfox 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 incidentfox/incidentfox. 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/incidentfox/incidentfox.svg)](https://repogeo.com/en/r/incidentfox/incidentfox)

HTML

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

Pro

Subscribe to Pro for deep diagnoses

incidentfox/incidentfox — 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