RRepoGEO

REPOGEO REPORT · LITE

zama-ai/tfhe-rs

Default branch main · commit 48b45ddb · scanned 6/25/2026, 7:16:20 AM

GitHub: 1,619 stars · 328 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

3 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
66 /100
Needs work
Category recall
1 / 2
Avg rank #2.0 when recommended
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 zama-ai/tfhe-rs, 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
  • highhomepage#1
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://docs.zama.org/tfhe-rs
  • highreadme#2
    Add a concise, direct statement of purpose to the README's opening

    Why:

    COPY-PASTE FIX
    Add this sentence right after the initial badge/link block, before the '## About' section:

"TFHE-rs is a pure Rust implementation of the TFHE scheme, enabling secure boolean and integer arithmetics directly on encrypted data."
  • mediumreadme#3
    Clarify the project's license(s) in the README

    Why:

    COPY-PASTE FIX
    Add a section or line in the README (e.g., under 'About' or a new 'License' section) stating: "This project is licensed under [Specify the actual license(s) here, e.g., 'a custom license based on Apache 2.0 and MIT']. Please see the LICENSE file for full details."

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
1 / 2
50% of queries surface zama-ai/tfhe-rs
Avg rank
#2.0
Lower is better. #1 = top recommendation.
Share of voice
8%
Of all named tools, what % are you?
Top rival
zama-ai/concrete
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. zama-ai/concrete · recommended 1×
  2. tuneinsight/lattigo · recommended 1×
  3. google/heir · recommended 1×
  4. seal-rs/seal-rs · recommended 1×
  5. Microsoft SEAL · recommended 1×
  • CATEGORY QUERY
    How can I perform computations on encrypted data using a Rust library?
    you: #2
    AI recommended (in order):
    1. Concrete (zama-ai/concrete)
    2. TFHE-rs (tfhe-rs/tfhe-rs) ← you
    3. Lattigo (tuneinsight/lattigo)
    4. HEIR (google/heir)
    5. seal-rs (seal-rs/seal-rs)
    Show full AI answer
  • CATEGORY QUERY
    What tools enable secure boolean and integer arithmetic on data without decrypting it?
    you: not recommended
    AI recommended (in order):
    1. Microsoft SEAL
    2. PALISADE
    3. TFHE (Concrete)
    4. IBM HElib
    5. MP-SPDZ
    6. SCALE-MAMBA
    7. Obliv-C

    AI recommended 7 alternatives but never named zama-ai/tfhe-rs. 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 zama-ai/tfhe-rs?
    pass
    AI named zama-ai/tfhe-rs explicitly

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

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

Subscribe to Pro for deep diagnoses

zama-ai/tfhe-rs — 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