REPOGEO REPORT · LITE
0xPARC/zk-bug-tracker
Default branch main · commit 56a99667 · scanned 6/6/2026, 8:58:16 AM
GitHub: 727 stars · 74 forks
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 0xPARC/zk-bug-tracker, 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.
- hightopics#1Add specific topics for ZK security and vulnerabilities
Why:
COPY-PASTE FIXzk-proofs, zero-knowledge, cryptography, security, vulnerabilities, exploits, bug-tracker, auditing, blockchain-security, web3-security
- highreadme#2Clarify the README's opening sentence to emphasize its nature as a practical, living database
Why:
CURRENTA community-maintained collection of bugs, vulnerabilities, and exploits in apps using ZK crypto.
COPY-PASTE FIXThis is a community-maintained, living database of bugs, vulnerabilities, and exploits specifically found in applications using Zero-Knowledge (ZK) cryptography.
- mediumabout#3Update the repository's 'About' description
Why:
CURRENTA community-maintained collection of bugs, vulnerabilities, and exploits in apps using ZK crypto.
COPY-PASTE FIXA community-maintained, living database of bugs, vulnerabilities, and exploits specifically found in applications using Zero-Knowledge (ZK) cryptography.
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.
- Cryptology ePrint Archive · recommended 1×
- CRYPTO · recommended 1×
- EUROCRYPT · recommended 1×
- ASIACRYPT · recommended 1×
- USENIX Security · recommended 1×
- CATEGORY QUERYWhere can I find a list of common vulnerabilities in zero-knowledge cryptography applications?you: not recommendedAI recommended (in order):
- Cryptology ePrint Archive
- CRYPTO
- EUROCRYPT
- ASIACRYPT
- USENIX Security
- CCS
- NDSS
- Trail of Bits
- NCC Group
- OpenZeppelin
- Ethereum Research Forum
- Zcash Community Forum/Research
- Axiom
- ZKProof Community
- Paradigm Research
- Scroll
- Polygon Zero
- StarkWare
- Aleo
- arkworks-rs
- bellman
- gnark
- circom
AI recommended 23 alternatives but never named 0xPARC/zk-bug-tracker. This is the gap to close.
Show full AI answer
- CATEGORY QUERYWhat are known exploits and security risks in ZK crypto projects for auditing purposes?you: not recommendedAI recommended (in order):
- Halo2 (Zcash/halo2)
- Gnark (ConsenSys/gnark)
- F* (FStarLang/FStar)
- Valgrind
- American Fuzzy Lop (AFL++) (AFLplusplus/AFLplusplus)
- libFuzzer
- Hardhat (NomicFoundation/hardhat)
- Foundry (foundry-rs/foundry)
- Rust's `cargo test`
- Slither (crytic/slither)
- Mythril (MythrilSec/mythril)
- Hardhat Gas Reporter (c-j-r-t/hardhat-gas-reporter)
- Foundry's `forge test --gas-report`
- Certora Prover
- Dafny (dafny-lang/dafny)
- TLA+
- Snyk
- Dependabot
- Prettier (prettier/prettier)
- ESLint (eslint/eslint)
- Rustfmt (rust-lang/rustfmt)
- `solidity-coverage` (sc-forks/solidity-coverage)
- `kcov` (SimonKagstrom/kcov)
AI recommended 23 alternatives but never named 0xPARC/zk-bug-tracker. This is the gap to close.
Show full AI answer
Objective checks
Rule-based audits of metadata signals AI engines weight most.
- Metadata completenesswarn
Suggestion:
- README presencepass
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 0xPARC/zk-bug-tracker?passAI named 0xPARC/zk-bug-tracker explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
- If a team adopts 0xPARC/zk-bug-tracker in production, what risks or prerequisites should they evaluate first?passAI named 0xPARC/zk-bug-tracker 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 0xPARC/zk-bug-tracker solve, and who is the primary audience?passAI named 0xPARC/zk-bug-tracker 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 0xPARC/zk-bug-tracker. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.
[](https://repogeo.com/en/r/0xPARC/zk-bug-tracker)<a href="https://repogeo.com/en/r/0xPARC/zk-bug-tracker"><img src="https://repogeo.com/badge/0xPARC/zk-bug-tracker.svg" alt="RepoGEO" /></a>Subscribe to Pro for deep diagnoses
0xPARC/zk-bug-tracker — 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