RRepoGEO

REPOGEO REPORT · LITE

Kodezi/Chronos

Default branch main · commit 4b95b9f8 · scanned 6/21/2026, 11:03:12 AM

GitHub: 4,919 stars · 212 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
40 /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
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 Kodezi/Chronos, 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
    Add a direct positioning statement to the README's introduction

    Why:

    COPY-PASTE FIX
    Add the following sentence immediately after the H1: 'Kodezi Chronos is the world's first debugging-first language model, achieving state-of-the-art results in autonomous bug fixing and repository-scale code understanding.'
  • highreadme#2
    Move model access notice to the README's introduction

    Why:

    CURRENT
    The 'Model Access Notice' is currently a section further down in the README.
    COPY-PASTE FIX
    Add the following paragraph immediately after the initial positioning statement: 'Please note: Chronos is a proprietary model, available exclusively through Kodezi OS starting Q1 2026.'
  • mediumlicense#3
    Clarify the project's license in the README

    Why:

    CURRENT
    The project has a LICENSE file, but its SPDX identifier is 'NOASSERTION' and the GitHub label is 'Other'.
    COPY-PASTE FIX
    Add a section or line in the README's 'License' section stating: 'This project's licensing terms are detailed in the LICENSE file. Please consult it for specific conditions and applicable licenses.'

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 Kodezi/Chronos
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Copilot
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Copilot · recommended 1×
  2. CodiumAI · recommended 1×
  3. Snyk Code · recommended 1×
  4. Tabnine · recommended 1×
  5. Pylint · recommended 1×
  • CATEGORY QUERY
    What AI tools can automatically fix bugs in my codebase with high accuracy?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot
    2. CodiumAI
    3. Snyk Code
    4. Tabnine
    5. Pylint
    6. SonarQube / SonarCloud

    AI recommended 6 alternatives but never named Kodezi/Chronos. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an intelligent assistant to help debug complex software projects and understand large codebases.
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot Chat
    2. Cursor
    3. Sourcegraph Cody (sourcegraph/cody)
    4. Tabnine Chat
    5. JetBrains AI Assistant
    6. OpenAI GPT-4

    AI recommended 6 alternatives but never named Kodezi/Chronos. 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 Kodezi/Chronos?
    pass
    AI named Kodezi/Chronos explicitly

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

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

Subscribe to Pro for deep diagnoses

Kodezi/Chronos — 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