RRepoGEO

REPOGEO REPORT · LITE

jlouis/fuse

Default branch master · commit 79d0817d · scanned 6/9/2026, 6:16:50 AM

GitHub: 513 stars · 51 forks

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 jlouis/fuse, 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 'Fuse' vs. 'FUSE' prominently in README

    Why:

    CURRENT
    *NOTE*: If you need to access FUSE (Filesystem in Userspace) then this is not the project you want. An Erlang implementation can be found in the *fuserl* project, fuserl on Google Code or fuserl on Github gives the pointers.
    COPY-PASTE FIX
    **IMPORTANT NOTE:** This project implements a *circuit breaker* pattern for Erlang. If you are looking for FUSE (Filesystem in Userspace) bindings, this is *not* the project you want. Please see `fuserl` for Erlang FUSE implementations.
  • hightopics#2
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    erlang, otp, circuit-breaker, fault-tolerance, resilience, microservices
  • mediumreadme#3
    Strengthen README opening to highlight problem solved

    Why:

    CURRENT
    # Fuse — A Circuit Breaker implementation for Erlang

This application implements a so-called circuit-breaker for Erlang.
    COPY-PASTE FIX
    # Fuse: An Erlang Circuit Breaker for Resilient Microservices and Fault Tolerance

This application provides a robust circuit breaker implementation for Erlang/OTP, designed to prevent cascading failures and enhance the resilience of distributed systems.

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 jlouis/fuse
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
OTP Supervisors
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. OTP Supervisors · recommended 1×
  2. erl_breaker · recommended 1×
  3. poolboy · recommended 1×
  4. gen_server · recommended 1×
  5. httpc · recommended 1×
  • CATEGORY QUERY
    How to implement fault tolerance for Erlang microservices to prevent cascading failures?
    you: not recommended
    AI recommended (in order):
    1. OTP Supervisors
    2. erl_breaker
    3. poolboy
    4. gen_server
    5. httpc
    6. ratelimit

    AI recommended 6 alternatives but never named jlouis/fuse. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best Erlang libraries for building resilient distributed systems with service protection?
    you: not recommended
    AI recommended (in order):
    1. OTP (Open Telecom Platform)
    2. Ranch
    3. Poolboy
    4. Partisan
    5. Gossip
    6. Erlang's `global` module

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

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

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

Subscribe to Pro for deep diagnoses

jlouis/fuse — 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