RRepoGEO

REPOGEO REPORT · LITE

kaplanelad/shellfirm

Default branch main · commit 7ebf8697 · scanned 6/16/2026, 2:36:55 AM

GitHub: 917 stars · 33 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 kaplanelad/shellfirm, 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 paragraph to clarify its unique 'interception + challenge' mechanism and target audience (humans AND AI agents).

    Why:

    CURRENT
    Humans make mistakes. AI agents make them faster. shellfirm intercepts dangerous shell commands before the damage is done.
    COPY-PASTE FIX
    Humans make mistakes. AI agents make them faster. Unlike simple aliases or system-level sandboxes, shellfirm intercepts dangerous shell commands *before* they execute, presenting an interactive challenge to confirm intent and prevent damage.
  • hightopics#2
    Add more specific topics related to AI agent safety and LLM security.

    Why:

    CURRENT
    agent, ai, captcha, devops, devops-tools, mcp, prompt, rust, shell, terminal, zsh
    COPY-PASTE FIX
    agent, ai, ai-safety, llm, llm-security, ai-agent, captcha, devops, devops-tools, mcp, prompt, rust, shell, terminal, zsh
  • mediumreadme#3
    Add a 'Why not X?' or 'How is this different?' section to the README, comparing `shellfirm` to common, simpler alternatives.

    Why:

    COPY-PASTE FIX
    ## Why shellfirm?
While simple aliases or tools like `safe-rm` can prevent some mistakes, `shellfirm` offers a comprehensive, context-aware solution. It goes beyond basic command blocking by actively intercepting a wide range of dangerous patterns across 9 ecosystems, escalating challenges based on context (e.g., SSH, root, protected branches), and suggesting safer alternatives. This provides a robust layer of protection that static aliases or simple wrappers cannot match, especially for complex scenarios and AI agent interactions.

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 kaplanelad/shellfirm
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
alias
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. alias · recommended 1×
  2. trash-cli · recommended 1×
  3. safe-rm · recommended 1×
  4. Git Hooks · recommended 1×
  5. GitLab · recommended 1×
  • CATEGORY QUERY
    How can I prevent accidental `rm -rf` or `git push --force` in my terminal?
    you: not recommended
    AI recommended (in order):
    1. alias
    2. trash-cli
    3. safe-rm
    4. Git Hooks
    5. GitLab
    6. GitHub Enterprise
    7. Bitbucket Server
    8. Shell Functions
    9. git push --force-with-lease

    AI recommended 9 alternatives but never named kaplanelad/shellfirm. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools add safety guardrails for AI agents running shell commands automatically?
    you: not recommended
    AI recommended (in order):
    1. Docker
    2. Firejail
    3. sudo
    4. AppArmor
    5. SELinux
    6. shlex
    7. Auditd
    8. OSSEC
    9. Wazuh
    10. Prometheus
    11. Grafana

    AI recommended 11 alternatives but never named kaplanelad/shellfirm. 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 kaplanelad/shellfirm?
    pass
    AI named kaplanelad/shellfirm explicitly

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

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

Subscribe to Pro for deep diagnoses

kaplanelad/shellfirm — 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