RRepoGEO

REPOGEO REPORT · LITE

apache/teaclave

Default branch main · commit ca646b8f · scanned 6/13/2026, 5:06:27 AM

GitHub: 801 stars · 157 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 apache/teaclave, 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 H1 and opening paragraph to emphasize SDKs

    Why:

    CURRENT
    # Apache Teaclave™: Empowering Building Memory Safe Trusted Applications in Confidential Computing

Welcome to the main repository of the **Teaclave** project, an open-source initiative under the Apache Software Foundation. Teaclave empowers developers to build **memory-safe** Trusted Applications across diverse **confidential computing platforms**, including Intel SGX and Arm TrustZone.

Originally built as a general-purpose secure computing framework, Teaclave has evolved into a vibrant ecosystem focused on **SDKs** that enable developers to directly build custom Trusted Applications. This shift has been driven by how the community naturally adopted and extended the project.
    COPY-PASTE FIX
    # Apache Teaclave™: A Rust SDK Ecosystem for Memory-Safe Trusted Applications in Confidential Computing

Welcome to the main repository of the **Teaclave** project, an open-source initiative under the Apache Software Foundation. Teaclave provides a vibrant **SDK ecosystem** for developers to build **memory-safe** Trusted Applications across diverse **confidential computing platforms**, including Intel SGX and Arm TrustZone.

This repository focuses on our **Rust-based SDKs** for various Trusted Execution Environments (TEEs). Please note that the previously hosted Teaclave FaaS framework, a general-purpose confidential computing platform, is no longer actively maintained here, as the community's focus has shifted to the SDKs.
  • mediumtopics#2
    Expand GitHub Topics to include SDK-specific terms

    Why:

    CURRENT
    confidential-computing, memory-safe, rust, sgx, tee, trusted-execution-environment, trustzone
    COPY-PASTE FIX
    confidential-computing, memory-safe, rust, sgx, tee, trusted-execution-environment, trustzone, sdk, rust-sdk, enclave-sdk, confidential-computing-sdk
  • mediumreadme#3
    Add a 'Comparison with other TEE SDKs' section to README

    Why:

    COPY-PASTE FIX
    ## Comparison with other TEE SDKs

(Add a section here comparing Teaclave's SDKs with other prominent TEE SDKs like Intel SGX SDK for Rust, Open Enclave SDK, or Occlum, highlighting Teaclave's unique features, target use cases, or architectural differences.)

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 apache/teaclave
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
occlum/occlum
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. occlum/occlum · recommended 2×
  2. Rust · recommended 1×
  3. Intel SGX SDK · recommended 1×
  4. openenclave/openenclave · recommended 1×
  5. rust-sgx/sgx_tstd · recommended 1×
  • CATEGORY QUERY
    How to build memory-safe applications for confidential computing using trusted execution environments?
    you: not recommended
    AI recommended (in order):
    1. Rust
    2. Intel SGX SDK
    3. Microsoft Open Enclave SDK (openenclave/openenclave)
    4. sgx_tstd (rust-sgx/sgx_tstd)
    5. Confidential Containers
    6. Kata Containers (kata-containers/kata-containers)
    7. Intel TDX
    8. Go
    9. CGO
    10. Gramine (gramineproject/gramine)
    11. Occlum (occlum/occlum)
    12. C++

    AI recommended 12 alternatives but never named apache/teaclave. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a Rust SDK to develop secure enclaves on Intel SGX or Arm TrustZone.
    you: not recommended
    AI recommended (in order):
    1. Intel SGX SDK for Rust (sgx-sdk) (rust-sgx/rust-sgx-sdk)
    2. Occlum (occlum/occlum)
    3. MesaTEE (Trusted Execution Environment) (mesatee/mesatee)
    4. Mbed OS (ARMmbed/mbed-os)
    5. Zephyr (zephyrproject-rtos/zephyr)
    6. OP-TEE (Open Portable Trusted Execution Environment) (OP-TEE/optee_os)

    AI recommended 6 alternatives but never named apache/teaclave. 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 apache/teaclave?
    pass
    AI named apache/teaclave explicitly

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

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

Subscribe to Pro for deep diagnoses

apache/teaclave — 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