RRepoGEO

REPOGEO REPORT · LITE

MozillaSecurity/funfuzz

Default branch master · commit 92179f60 · scanned 6/12/2026, 12:37:13 AM

GitHub: 642 stars · 113 forks

AI VISIBILITY SCORE
28 /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
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 MozillaSecurity/funfuzz, 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 README's opening to emphasize JavaScript engine security testing

    Why:

    CURRENT
    This repository contains several JavaScript-based fuzzers. [jsfunfuzz](js/jsfunfuzz) tests JavaScript engines and can run in a JavaScript shell...
    COPY-PASTE FIX
    This repository provides a collection of JavaScript-based fuzzers and a harness specifically designed for automated security testing and vulnerability discovery in JavaScript engines like SpiderMonkey.
  • mediumhomepage#2
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    https://github.com/MozillaSecurity/funfuzz
  • lowtopics#3
    Expand repository topics for greater specificity in JavaScript engine security

    Why:

    CURRENT
    fuzzer, javascript-fuzzing, jsfunfuzz, spidermonkey-engine
    COPY-PASTE FIX
    fuzzer, javascript-fuzzing, jsfunfuzz, spidermonkey-engine, javascript-security, vulnerability-discovery, engine-fuzzing, security-testing

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 MozillaSecurity/funfuzz
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
AFL++
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. AFL++ · recommended 1×
  2. LibFuzzer · recommended 1×
  3. DOMPurify · recommended 1×
  4. Jalangi2 · recommended 1×
  5. js-fuzzer · recommended 1×
  • CATEGORY QUERY
    How to automatically generate test cases for JavaScript engine security testing?
    you: not recommended
    AI recommended (in order):
    1. AFL++
    2. LibFuzzer
    3. DOMPurify
    4. Jalangi2
    5. js-fuzzer
    6. ANTLR
    7. Zest

    AI recommended 7 alternatives but never named MozillaSecurity/funfuzz. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tooling for automated JavaScript engine vulnerability discovery and crash analysis using Python?
    you: not recommended
    AI recommended (in order):
    1. AFL++ (AFLplusplus/AFLplusplus)
    2. libFuzzer (llvm/llvm-project)
    3. Radare2 (radareorg/radare2)
    4. GDB
    5. PwnTools (Gallopsled/pwntools)
    6. Frida (frida/frida)
    7. Triton (JonathanSalwan/Triton)

    AI recommended 7 alternatives but never named MozillaSecurity/funfuzz. 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 MozillaSecurity/funfuzz?
    pass
    AI named MozillaSecurity/funfuzz explicitly

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

  • If a team adopts MozillaSecurity/funfuzz in production, what risks or prerequisites should they evaluate first?
    pass
    AI named MozillaSecurity/funfuzz 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 MozillaSecurity/funfuzz solve, and who is the primary audience?
    pass
    AI did not name MozillaSecurity/funfuzz — 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?

Embed your GEO score

Drop this badge into the README of MozillaSecurity/funfuzz. 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/MozillaSecurity/funfuzz.svg)](https://repogeo.com/en/r/MozillaSecurity/funfuzz)
HTML
<a href="https://repogeo.com/en/r/MozillaSecurity/funfuzz"><img src="https://repogeo.com/badge/MozillaSecurity/funfuzz.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

MozillaSecurity/funfuzz — 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