SDKs, apps & benchmarks

Every SDK, integration, app, and benchmark repo in the org.

Snapshot date: 2026-10-19. Sources: gh repo list Lore-Hex (47 repos), gh api (fork/parent, commits, releases), shallow clones of each repo (READMEs, manifests, workflows, PARITY docs), and public registry lookups (PyPI, npm, crates.io, proxy.golang.org, Maven Central).

Scope: the 32 repos below. The other 15 (quill-router, quill-cloud-proxy, quill-cloud-infra, trustedrouter-confidential-stack, token-exchange-neocloud-in-a-box, trustedrouter-onprem, trustedrouter-provider-check, lightning-router, reverse-harness, TrustedRouter-Fusion-Draco, SREChat, OpenChat, AllRouter, BurstyRouter, trustedrouter-eu) are in 09-repos-platform.md. 32 + 15 = 47, so every repo in the org is covered by one of the two docs. All repos are public. None are archived.

"30d commits" counts commits on the default branch since 2026-09-19. Many repos show a last commit of 2026-08-16. On that date the same CODEOWNERS and SECURITY.md commits landed across the org, so 2026-08-16 usually means "no real work since then."

1. Master table

Activity summary. Repos with active work in the last 30 days: trusted-router-js (21), confidential-cowork-desktop (7), trusted-router-rust (5), QuiLLM (5), and py/go/java/swift/conformance (3–4 each). Repos dormant since mid-August: most third-party integrations, all R/agent forks, all benchmarks except FreedomBench and PrometheusBench (both early September).

Version drift and gotchas. - GitHub Releases pages lag the registries. py shows release v0.5.0 while PyPI has 0.9.0. js shows v0.7.0 while npm has 0.10.1. Java shows v0.2.1 while the latest tag is v0.4.0. Treat tags and registries as the source of truth, not the Releases page. - The Java SDK's README advertises Maven Central 0.4.0, but the artifact cannot be found on Central. Check this before telling customers to use it. - trustedrouter-ai-sdk-provider is not on npm, although the README says npm install @trustedrouter/ai-sdk-provider. Its publish workflow only runs on a GitHub Release, and none has been cut. - Swift tags have no v prefix (0.9.0). Every other SDK uses vX.Y.Z. - Apps pin old SDKs. confidential-cowork-desktop pins @lore-hex/trusted-router 0.4.0, while npm has 0.10.1. QuillCode requires trusted-router-swift from: 0.6.1. - The confidential-cowork-desktop repo description says "based on Pi Desktop", but its README and UPSTREAM.md say it is a port of OpenCode 2.0.32. The Pi-based product is trpi.

2. SDK feature matrix

Built from each SDK's README and PARITY.md, plus source greps. "Y" means a dedicated public API. "via builder/alias" means it is reachable through the orchestration tool builders or the trustedrouter/fusion model alias, without a dedicated method.

The Go PARITY.md is the reference for the "two-plane routing" and "stream-open retry" divergences from the older py/js behavior. Rust and Java PARITY.md say they follow the Go contract.

3. SDKs: testing, release, and conformance

trusted-router-sdk-conformance

• What it is: one black-box suite run against all six SDKs. A thin per-language driver (drivers/{python,javascript,go,rust,java,swift}) calls the SDK's real public API. The driver points https://api.trustedrouter.com at an ephemeral TLS loopback fault server with a throwaway CA. A shared oracle then checks both the normalized result and the wire transcript.
• Scenarios (25, scenarios/*.json): success; retry on 503, 500, and 429; x-should-retry true/false verdicts; retry exhaustion; transport disconnect; telemetry across retries; reserved-header opt-out; terminal 401; truncated and malformed SSE; cross-origin redirect; generated idempotency keys (with and without a disconnect); unsafe POST replay; body timeout; caller cancellation; credential-free OAuth plus OAuth redirect; chat and Responses typed-model preservation; retry on a truncated or stalled error body.
• Coverage (docs/coverage.md): all 6 SDKs pass all 7 capability groups (core retry and telemetry, SSE integrity, redirect isolation, safe replay, body timeout and cancellation, credential-free OAuth, typed model preservation). The v0.2 gate allows no skips.
• Not covered by the shared matrix: regional affinity/failover, first-frame streaming deadlines, SSE heartbeat idle timing, and cryptographic attestation validation. Each SDK covers these only in its own native tests.
• Wiring: each SDK's conformance.yml calls the reusable workflow Lore-Hex/trusted-router-sdk-conformance/.github/workflows/sdk-pr.yml@main on PRs. The harness's own conformance.yml runs on PR and push, nightly (cron 17 4 * * *), and on repository_dispatch (sdk-conformance). Its manual dispatch takes a ref input for each SDK.
• Not covered at all: the integrations, apps, and benchmarks. Integrations do not use the SDKs (see §4).

4. Integrations and plugins

Every first-party integration is a thin OpenAI-compatible wrapper. Each one points at https://api.trustedrouter.com/v1 and reads the model catalog from GET /v1/models. None of them depends on an official SDK, so none of them gets attestation, receipts, or SDK retry semantics, and the conformance suite does not cover them.

Upstream-contribution forks (staging branches only; main is just the CODEOWNERS/SECURITY commits)

The forks are thousands of commits behind upstream (openclaw: 63,960; hermes: 43,577). Don't build on their main. Rebase the TR branch onto upstream when refreshing a PR.

5. Apps

6. Benchmarks

None of the benchmarks has CI. They are research artifacts, so expect them to be run by hand.

7. Ecosystem layers

flowchart TB
  subgraph Apps["Apps (end-user products)"]
    QC["QuillCode<br/>Quill Cowork + Confidential Cowork (Swift)"]
    CCD["confidential-cowork-desktop<br/>Trusted Cowork (OpenCode port)"]
    TRPI["trpi<br/>tr-cowork CLI (Pi)"]
    FW["FastWorker (openworker fork)"]
  end
  subgraph Bench["Benchmarks / research"]
    PB["PrometheusBench"]; FB["FreedomBench"]; TB["trustedrouter-benchmarks"]
    BMB["prometheus-biomysterybench"]; XB["TR-/Prometheus-ExploitBench"]
  end
  subgraph Integrations["Third-party framework integrations (OpenAI-compatible, no SDK)"]
    LLM["llm-trustedrouter"]; OC["openclaw-trustedrouter"]; HM["hermes-trustedrouter"]
    AZ["agent-zero-trustedrouter"]; N8N["n8n-nodes-trustedrouter"]; LI["llama-index-llms-trustedrouter"]
    AIS["trustedrouter-ai-sdk-provider"]; R["aisdk / aisdk.providers (R forks)"]; ADV["LLM-advisor (skill + MCP)"]
  end
  subgraph SDKs["Official SDKs (gated by trusted-router-sdk-conformance)"]
    PY["trusted-router-py"]; JS["trusted-router-js (+CLI)"]; GO["trusted-router-go"]
    RS["trusted-router-rust (+C ABI)"]; JV["trusted-router-java"]; SW["trusted-router-swift"]
    CONF["trusted-router-sdk-conformance"]
  end
  subgraph API["TrustedRouter API (quill-router / quill-cloud-proxy)"]
    INF["Inference plane<br/>api.trustedrouter.com/v1<br/>chat, responses, messages, embeddings, fusion, /attestation"]
    CTL["Control plane<br/>trustedrouter.com/v1<br/>models, credits, billing, broadcast, oauth"]
    TRUST["trust.trustedrouter.com<br/>trust release / JWKS"]
  end

  QC --> SW
  CCD --> JS
  TRPI --> INF
  FW --> INF
  PB --> PY
  FB --> PY
  TB --> PY
  BMB --> INF
  XB --> INF
  LLM & OC & HM & AZ & N8N & LI & AIS & R --> INF
  ADV --> CTL
  CONF -. fault-injection tests .-> PY & JS & GO & RS & JV & SW
  PY & JS & GO & RS & JV & SW --> INF
  PY & JS & GO & RS & JV & SW --> CTL
  PY & JS & GO & RS & JV & SW --> TRUST

flowchart TB
  subgraph Apps["Apps (end-user products)"]
    QC["QuillCode<br/>Quill Cowork + Confidential Cowork (Swift)"]
    CCD["confidential-cowork-desktop<br/>Trusted Cowork (OpenCode port)"]
    TRPI["trpi<br/>tr-cowork CLI (Pi)"]
    FW["FastWorker (openworker fork)"]
  end
  subgraph Bench["Benchmarks / research"]
    PB["PrometheusBench"]; FB["FreedomBench"]; TB["trustedrouter-benchmarks"]
    BMB["prometheus-biomysterybench"]; XB["TR-/Prometheus-ExploitBench"]
  end
  subgraph Integrations["Third-party framework integrations (OpenAI-compatible, no SDK)"]
    LLM["llm-trustedrouter"]; OC["openclaw-trustedrouter"]; HM["hermes-trustedrouter"]
    AZ["agent-zero-trustedrouter"]; N8N["n8n-nodes-trustedrouter"]; LI["llama-index-llms-trustedrouter"]
    AIS["trustedrouter-ai-sdk-provider"]; R["aisdk / aisdk.providers (R forks)"]; ADV["LLM-advisor (skill + MCP)"]
  end
  subgraph SDKs["Official SDKs (gated by trusted-router-sdk-conformance)"]
    PY["trusted-router-py"]; JS["trusted-router-js (+CLI)"]; GO["trusted-router-go"]
    RS["trusted-router-rust (+C ABI)"]; JV["trusted-router-java"]; SW["trusted-router-swift"]
    CONF["trusted-router-sdk-conformance"]
  end
  subgraph API["TrustedRouter API (quill-router / quill-cloud-proxy)"]
    INF["Inference plane<br/>api.trustedrouter.com/v1<br/>chat, responses, messages, embeddings, fusion, /attestation"]
    CTL["Control plane<br/>trustedrouter.com/v1<br/>models, credits, billing, broadcast, oauth"]
    TRUST["trust.trustedrouter.com<br/>trust release / JWKS"]
  end

  QC --> SW
  CCD --> JS
  TRPI --> INF
  FW --> INF
  PB --> PY
  FB --> PY
  TB --> PY
  BMB --> INF
  XB --> INF
  LLM & OC & HM & AZ & N8N & LI & AIS & R --> INF
  ADV --> CTL
  CONF -. fault-injection tests .-> PY & JS & GO & RS & JV & SW
  PY & JS & GO & RS & JV & SW --> INF
  PY & JS & GO & RS & JV & SW --> CTL
  PY & JS & GO & RS & JV & SW --> TRUST

8. Which repo do I touch for X?

9. Open issues worth a CTO's attention

1. Java is not on Maven Central, although the README and release workflow say it is. Check the Sonatype credentials and namespace for com.trustedrouter.
2. The Vercel AI SDK provider was never published. It needs a GitHub Release, and the npm scope @trustedrouter has to exist.
3. Integrations skip the SDKs. They lose attestation, receipts, and SDK retry semantics, and the conformance suite cannot cover them. Decide whether that is acceptable or whether the Python and TS integrations should wrap trusted-router-py / @lore-hex/trusted-router.
4. confidential-cowork-desktop pins SDK 0.4.0, six minors behind npm 0.10.1. This is a confidential-tier product.
5. Attestation validation and regional failover are not in the shared conformance matrix. docs/coverage.md says so explicitly.
6. The Releases pages are stale for py, js, and java. Customers and agents who read them will see wrong versions.