RRepoGEO

REPOGEO REPORT · LITE

muety/wakapi

Default branch master · commit 26c2e4e0 · scanned 5/28/2026, 2:42:39 PM

GitHub: 4,318 stars · 288 forks

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 muety/wakapi, 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
  • highabout#1
    Refine the 'About' description to emphasize personal coding statistics and productivity

    Why:

    CURRENT
    📊 A minimalist, self-hosted WakaTime-compatible backend for coding statistics
    COPY-PASTE FIX
    📊 A minimalist, self-hosted, open-source backend for tracking personal coding statistics and developer productivity, compatible with WakaTime.
  • mediumreadme#2
    Add a 'Comparison to Alternatives' section in the README

    Why:

    COPY-PASTE FIX
    Add a new section, e.g., '## 🆚 Comparison to Alternatives' or '## 💡 Why Wakapi?', with a brief table or bullet points comparing Wakapi to WakaTime, ActivityWatch, and Code::Stats, highlighting its self-hosted, open-source, and privacy-focused aspects.
  • lowtopics#3
    Add 'open-source' to the repository topics

    Why:

    CURRENT
    coding-statistics, developer-tools, productivity, self-hosted, time-tracker, wakatime, wakatime-api
    COPY-PASTE FIX
    coding-statistics, developer-tools, open-source, productivity, self-hosted, time-tracker, wakatime, wakatime-api

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 muety/wakapi
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
WakaTime
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. WakaTime · recommended 1×
  2. ActivityWatch/activitywatch · recommended 1×
  3. code-stats/code-stats · recommended 1×
  4. gitstats/gitstats · recommended 1×
  5. go-gitea/gitea · recommended 1×
  • CATEGORY QUERY
    What are the best self-hosted solutions for tracking personal coding statistics and productivity?
    you: not recommended
    AI recommended (in order):
    1. WakaTime
    2. ActivityWatch (ActivityWatch/activitywatch)
    3. Code::Stats (code-stats/code-stats)
    4. GitStats (gitstats/gitstats)
    5. Gitea (go-gitea/gitea)
    6. GitLab (gitlab-org/gitlab)

    AI recommended 6 alternatives but never named muety/wakapi. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an open-source, self-hostable backend for collecting and visualizing developer activity data.
    you: not recommended
    AI recommended (in order):
    1. Grafana
    2. Prometheus
    3. git-exporter
    4. jenkins-exporter
    5. github-exporter
    6. ELK Stack
    7. Elasticsearch
    8. Logstash
    9. Kibana
    10. Metabase
    11. PostgreSQL
    12. Supabase
    13. AppFlowy
    14. NocoDB

    AI recommended 14 alternatives but never named muety/wakapi. 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 muety/wakapi?
    pass
    AI named muety/wakapi explicitly

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

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

Subscribe to Pro for deep diagnoses

muety/wakapi — 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