RRepoGEO

REPOGEO REPORT · LITE

zvtvz/zvt

Default branch master · commit f971f00c · scanned 5/27/2026, 4:46:57 PM

GitHub: 4,147 stars · 983 forks

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 zvtvz/zvt, 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 the README's opening to clearly state its purpose

    Why:

    CURRENT
    The origin of ZVT
The Three Major Principles of Stock Trading
Declaration...
    COPY-PASTE FIX
    Start the README with a concise, benefit-oriented paragraph that immediately positions `zvt` as a comprehensive, modular framework for quantitative trading, backtesting, and building ML-driven bots for stocks and cryptocurrencies.
  • mediumreadme#2
    Add a dedicated section highlighting unique features and differentiators

    Why:

    COPY-PASTE FIX
    Add a dedicated section (e.g., 'Key Features' or 'Why ZVT?') to the README that explicitly lists its strengths, such as integrated data acquisition (mentioning Chinese markets if relevant), comprehensive backtesting, visual UI (Dash & Plotly), and support for ML-driven strategies.
  • mediumreadme#3
    Include a quick start example or key use cases in the README

    Why:

    COPY-PASTE FIX
    Add a 'Quick Start Example' or 'Key Use Cases' section to the README with a minimal, runnable code snippet demonstrating a core feature like backtesting a simple strategy or acquiring data, to immediately showcase its functionality.

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 zvtvz/zvt
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Zipline
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Zipline · recommended 1×
  2. Backtrader · recommended 1×
  3. PyAlgoTrade · recommended 1×
  4. QuantConnect (Lean Engine) · recommended 1×
  5. Catalyst · recommended 1×
  • CATEGORY QUERY
    What are good Python frameworks for developing and backtesting quantitative trading strategies?
    you: not recommended
    AI recommended (in order):
    1. Zipline
    2. Backtrader
    3. PyAlgoTrade
    4. QuantConnect (Lean Engine)
    5. Catalyst
    6. VectorBT
    7. Pandas TA

    AI recommended 7 alternatives but never named zvtvz/zvt. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a modular platform for building ML-driven trading bots for stocks and cryptocurrencies.
    you: not recommended
    AI recommended (in order):
    1. QuantConnect (Lean) (QuantConnect/Lean)
    2. Quantopian (Zipline) (quantopian/zipline)
    3. Backtrader (mementum/backtrader)
    4. Alpaca Trade API
    5. Gekko (askmike/gekko)
    6. Freqtrade (freqtrade/freqtrade)

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

Subscribe to Pro for deep diagnoses

zvtvz/zvt — 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