RRepoGEO

REPOGEO REPORT · LITE

feicong/re-docs

Default branch master · commit 99d07c4f · scanned 6/16/2026, 8:08:16 AM

GitHub: 575 stars · 198 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 feicong/re-docs, 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 clarify its purpose as a collection of notes

    Why:

    CURRENT
    # 逆向笔记
    COPY-PASTE FIX
    # 逆向笔记 / Reverse Engineering Notes

This repository is a collection of personal notes and guides on reverse engineering, focusing on environment setup for security researchers and detailed analysis of Lua programs (bytecode, LuaJIT, IDA Pro integration).
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://github.com/feicong/re-docs
  • lowtopics#3
    Expand repository topics to include broader reverse engineering terms

    Why:

    CURRENT
    010editor, lua, luadec, luajit, reverse-engineering
    COPY-PASTE FIX
    010editor, lua, luadec, luajit, reverse-engineering, security-research, exploit-development, binary-analysis, malware-analysis

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 feicong/re-docs
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
IDA Pro
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. IDA Pro · recommended 2×
  2. Ghidra · recommended 2×
  3. LuaDec · recommended 1×
  4. LuaJIT · recommended 1×
  5. Lua · recommended 1×
  • CATEGORY QUERY
    How do I analyze and reverse engineer Lua bytecode and compiled scripts?
    you: not recommended
    AI recommended (in order):
    1. LuaDec
    2. LuaJIT
    3. Lua
    4. LuaInspect
    5. IDA Pro
    6. Ghidra

    AI recommended 6 alternatives but never named feicong/re-docs. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best practices for setting up a reverse engineering environment for scripting languages?
    you: not recommended
    AI recommended (in order):
    1. Git
    2. pdb
    3. IPython
    4. PyCharm
    5. Node.js Inspector
    6. Chrome DevTools
    7. VS Code Debugger
    8. byebug
    9. pry
    10. Xdebug
    11. PhpStorm
    12. uncompyle6
    13. dis
    14. JD-GUI
    15. CFR
    16. Fernflower
    17. IntelliJ IDEA
    18. luadec
    19. php-deobfuscator
    20. VS Code
    21. Sublime Text
    22. WebStorm
    23. RubyMine
    24. ESLint
    25. Pylint
    26. Flake8
    27. RuboCop
    28. PHP_CodeSniffer
    29. pipdeptree
    30. npm list
    31. strace
    32. DTrace
    33. perf
    34. Burp Suite
    35. OWASP ZAP
    36. mitmproxy
    37. VirtualBox
    38. VMware Workstation Player
    39. Docker
    40. grep
    41. ack
    42. ag (the_silver_searcher)
    43. rg (ripgrep)
    44. sed
    45. awk
    46. Markdown
    47. Obsidian
    48. Joplin
    49. Notion
    50. IDA Pro
    51. Ghidra

    AI recommended 51 alternatives but never named feicong/re-docs. 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 feicong/re-docs?
    pass
    AI named feicong/re-docs explicitly

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

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

Subscribe to Pro for deep diagnoses

feicong/re-docs — 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