vouch-protocol 1.6.2__tar.gz → 2.0.1__tar.gz

{vouch_protocol-1.6.2/vouch_protocol.egg-info → vouch_protocol-2.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vouch-protocol
-Version: 1.6.2
+Version: 2.0.1
 Summary: The Identity & Reputation Standard for AI Agents
 Author-email: Vouch Protocol Contributors <hello@vouch-protocol.com>
 License: Apache License 2.0
@@ -229,10 +229,14 @@ Provides-Extra: langchain
 Requires-Dist: langchain>=0.1.0; extra == "langchain"
 Provides-Extra: crewai
 Requires-Dist: crewai>=0.1.0; extra == "crewai"
+Provides-Extra: langgraph
+Requires-Dist: langgraph>=0.1.0; extra == "langgraph"
+Provides-Extra: goose
+Requires-Dist: pyyaml>=6.0; extra == "goose"
 Provides-Extra: autogen
 Requires-Dist: pyautogen>=0.2.0; extra == "autogen"
 Provides-Extra: mcp
-Requires-Dist: mcp>=1.2.0; extra == "mcp"
+Requires-Dist: mcp>=0.1.0; extra == "mcp"
 Provides-Extra: vertex
 Requires-Dist: google-cloud-aiplatform>=1.0.0; extra == "vertex"
 Provides-Extra: streamlit
@@ -250,6 +254,8 @@ Requires-Dist: google-cloud-kms>=2.0.0; extra == "gcp"
 Provides-Extra: azure
 Requires-Dist: azure-keyvault-keys>=4.0.0; extra == "azure"
 Provides-Extra: pq
+Provides-Extra: udna
+Requires-Dist: sirraya-udna-sdk>=1.0.3; extra == "udna"
 Provides-Extra: tracing
 Requires-Dist: opentelemetry-api>=1.20.0; extra == "tracing"
 Requires-Dist: opentelemetry-sdk>=1.20.0; extra == "tracing"
@@ -271,7 +277,7 @@ Requires-Dist: base58>=2.1.0; extra == "dev"
 Requires-Dist: qrcode>=7.4.0; extra == "dev"
 Requires-Dist: c2pa-python>=0.5.0; extra == "dev"
 Provides-Extra: all
-Requires-Dist: vouch-protocol[autogen,crewai,dev,enterprise,langchain,mcp,server,streamlit,tracing,vertex]; extra == "all"
+Requires-Dist: vouch-protocol[autogen,crewai,dev,enterprise,goose,langchain,langgraph,mcp,server,streamlit,tracing,vertex]; extra == "all"
 Dynamic: license-file
 
 # Vouch Protocol™
@@ -280,9 +286,9 @@ Dynamic: license-file
  <img src="docs/assets/vouch-wordmark.png" alt="Vouch Protocol" width="400">
 </p>
 
-<sub><em>Vouch Protocol™ — common-law trademark.</em></sub>
+<sub><em>Vouch Protocol™ is a common-law trademark.</em></sub>
 
-<p align="center">The Open Standard for Identity & Provenance of AI Agents</strong>
+<p align="center"><strong>The Open Standard for Identity & Provenance of AI Agents</strong>
 </p>
 
 <p align="center">
@@ -299,6 +305,10 @@ Dynamic: license-file
  <a href="https://discord.gg/mMqx5cG9Y"><img src="https://img.shields.io/badge/Discord-Join_Community-7289da?logo=discord&logoColor=white" alt="Discord"></a>
 </p>
 
+<p align="center">
+ <a href="https://codespaces.new/vouch-protocol/vouch"><img src="https://github.com/codespaces/badge.svg" alt="Open in GitHub Codespaces" height="28"></a>
+</p>
+
 <p align="center">
  <a href="https://github.com/vouch-protocol/vouch/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="Apache 2.0 License"></a>
 </p>
@@ -307,6 +317,16 @@ Dynamic: license-file
 
 ## Quick Start
 
+```bash
+# Install (Linux and macOS). On Windows, use: pip install vouch-protocol
+curl -fsSL https://vouch-protocol.com/install.sh | sh
+
+# Run vouch with no arguments and pick what you want to do
+vouch
+```
+
+Prefer to do it by hand? It is three commands:
+
 ```bash
 pip install vouch-protocol
 
@@ -317,6 +337,8 @@ vouch git init
 git commit -m "Secure commit"
 ```
 
+Setting up an agent instead of git signing? `vouch onboard --quick` generates a working identity, allow-list, verifier, and heartbeat config in one command.
+
 ---
 
 ## What's New in v1.0
@@ -329,7 +351,7 @@ Vouch Protocol v1.0 aligns directly with the open standard:
 - **Hybrid post-quantum profile** (`hybrid-eddsa-mldsa44-jcs-2026`) as an optional add-on for regulated deployments aligning with NIST CNSA 2.0 / NSM-10 timelines.
 - **Three-way cross-implementation interop** verified across Python, TypeScript, and Go.
 
-The legacy v0.x JWS API (`Signer.sign()`, `Verifier.verify()`) continues to work unchanged for a deprecation window. New code should prefer `Signer.sign_credential()` and `Verifier.verify_credential()`. See the Specification at [vouch-protocol.com/specs/SPEC/](https://vouch-protocol.com/specs/SPEC/) for the full specification.
+Credentials are issued with `Signer.sign()` and checked with `Verifier.verify()`. See the Specification at [vouch-protocol.com/specs/SPEC/](https://vouch-protocol.com/specs/SPEC/) for the full specification.
 
 ---
 
@@ -356,11 +378,13 @@ Vouch is not one tool, it is a set of them. Here is the whole map.
 - **Vouch Shield** a runtime check that inspects every tool call against your rules, like a customs officer at the door.
 - **Continuous trust** heartbeats and session vouchers, so trust is a live signal that has to be renewed, not a badge that is issued once and trusted forever.
 
-### Framework integrations (coming soon)
-Standalone packages that drop Vouch into the agent framework you already use. Each one issues a verifiable credential for a tool call, with optional delegation back to a human principal. Landing on PyPI with v1.6.2.
+### Framework integrations (new in v1.6.2)
+Standalone packages that drop Vouch into the agent framework you already use. Each one issues a verifiable credential for a tool call, with optional delegation back to a human principal.
 - **`vouch-langchain`** a LangChain tool that signs each tool call before it leaves the agent.
+- **`vouch-langgraph`** signs LangGraph tool calls and graph nodes, so a signed trail runs across the whole graph.
 - **`vouch-crewai`** a CrewAI tool, with supervisor-to-worker delegation that can only narrow authority, never widen it.
 - **`vouch-a2a`** binds an A2A (Agent2Agent) Agent Card to a Vouch identity, so two agents can verify each other before they collaborate.
+- **`vouch-goose`** registers the Vouch MCP server as an extension for Block's Goose agent, so a Goose session can sign and verify out of the box.
 - **`vouch-mlflow`** signs an MLflow model artifact at registration time, bound to a content digest so any change to the weights breaks the signature.
 - **`vouch-safetensors`** embeds a credential in a `.safetensors` header, complementary to OpenSSF Model Signing, so a model carries who produced it.
 
@@ -370,7 +394,7 @@ The standalone **`vouch-mcp`** package above ships alongside these in v1.6.2.
 Python, TypeScript, and Go are the full reference implementations. A Rust core with idiomatic Swift, JVM (Java and Kotlin), .NET, and C wrappers shares one codebase, so every language produces byte-identical output, verified against shared test vectors. A WebAssembly build is included for the browser and the edge. See the table further down for status per language.
 
 ### Robots and embodied agents
-A robot is an agent with a body, so the same primitives apply: a `did:vouch:agent` identity, delegation chains for who authorized it, and continuous trust for whether it is still behaving. Vouch adds a hardware-root-of-trust profile, so a robot's secure element (a TPM or a secure enclave) anchors its DID and signs its heartbeats, binding identity to the physical device rather than a config file. This is the open identity layer; richer robot-lifecycle tooling builds on top of it. See the open `did:vouch:agent` profile in [docs/specs/](docs/specs/).
+A robot is an agent with a body, so identity and accountability matter even more once it can cause physical harm. The `vouch.robotics` module ships six capabilities on the same `eddsa-jcs-2022` credentials as the rest of Vouch: hardware-rooted identity (bound to a TPM or secure element, so it cannot be cloned to other hardware), model and config provenance (re-signable on every OTA update), physical capability scope (force, speed, a tighter cap near humans, allowed zones, and shift windows, checked before each actuation, with narrow-only delegation), a robot-to-robot trust handshake, an encrypted tamper-evident black box with a verifiable kill switch, and a scannable offline passport. All six are implemented in Python, TypeScript, Go, and the Rust core, which flows to the Swift, Kotlin/JVM, .NET, C/C++, and WebAssembly wrappers, so a robotics credential signed in one language verifies in every other. Fourteen further capabilities round out the set: a living-trust heartbeat (a signed per-interval motion summary whose trust decays unless it is renewed in-envelope), two-level credential revocation (per-credential status lists and whole-DID kill), an accountable safety record (a tamper-evident incident ledger summarized into a portable signed record), signed perception provenance (each captured sensor frame's hash bound to the robot's key and hash-linked, so a robot can prove what its sensors saw and a substituted frame is detectable), an offline delegation lease (a short-lived, scope-bounded grant a disconnected robot verifies and acts on with no network call, nesting across vendors), a physical quorum (a cryptographic two-person rule requiring M of N attested approvers for a high-consequence action), lifecycle credentials (ownership transfer that chains into a verifiable chain of custody, key rotation that forms a key history, and a signed decommission that retires the robot), a regulatory conformance profile (a machine-checkable mapping from a robot's credentials to the clauses of ISO 10218 and 15066, the EU Machinery Regulation, the EU AI Act, and UL 3300, with a deterministic checker and a signed conformance attestation), post-quantum signing by default (robot credentials sign with the hybrid classical-plus-ML-DSA-44 cryptosuite, with backward-compatible verification, so a robot stays unforgeable across its decade-long life), and cross-embodiment identity continuity (an agent identity that moves between robot bodies, with an embodiment credential re-binding to each body's hardware root and a continuity chain that proves the same accountable agent persisted, plus a fork check), a physical custody handoff chain (a signed record of who accepted custody of a task or object at each hop across human and robot actors, so an incident traces to the exact hop and an attested condition localizes damage to the holder responsible), bounded infrastructure access (an operator-signed grant naming a resource, its permitted operations, an optional zone, and a time window, which a robot pairs with a signed request the resource authorizes offline, so a robot can open a door or dock at a charger with a tamper-evident, attributable, shrink-only record), fused-sensor provenance (a signed attestation binding a robot's fused world model to the exact set of input frame hashes and the fusion method that produced it, so a manipulated fusion result or a dropped input is detectable and every fused input traces to a frame the robot recorded), and wear and degradation attestation (a robot signs its own wear level bound to its identity and hash-linked over time, and a deterministic rule narrows its physical capability scope as it degrades, so a worn robot operates inside a tighter, verifiable envelope than the static limit it shipped with), implemented across the same languages and pinned by the shared interop vector. See [docs/robotics.md](docs/robotics.md) and the defensive disclosures PAD-064 through PAD-070, PAD-076 through PAD-084, and PAD-087 through PAD-092.
 
 ### Inside your AI tools
 - **Claude Skill**, **OpenAI Custom GPT**, and **Gemini Gem** packages that teach your AI assistant how to add Vouch to your code, running on your own AI subscription.
@@ -420,7 +444,6 @@ AI agents are making real-world API calls with **ZERO cryptographic proof** of:
 - **Human-readable JSON** (proof attaches as a sibling object, no Base64-wrapped opaque payload)
 - **Framework-agnostic** (works with MCP, LangChain, CrewAI, AutoGPT, AutoGen, Vertex AI)
 - **Cross-language interop** (Python, TypeScript, Go, byte-identical canonical form)
-- **Backward-compatible** (legacy v0.x JWS API still supported during deprecation window)
 - **Open source** (Apache 2.0 license, CC0 prior-art portfolio)
 
 **Think of it as:**
@@ -442,9 +465,9 @@ flowchart LR
   V{"✅ Verified"}
 
   P -->|"Delegation VC"| A
-  A -->|"sign_credential(intent)"| C
+  A -->|"sign(intent)"| C
   C -->|"HTTP body<br/>application/vc+vouch"| API
-  API -->|"verify_credential()"| V
+  API -->|"verify()"| V
 ```
 
 **4 Simple Steps:**
@@ -502,6 +525,10 @@ flowchart TB
 
 ### 1. Install
 ```bash
+# Linux and macOS: one line
+curl -fsSL https://vouch-protocol.com/install.sh | sh
+
+# Or with pip (any platform)
 pip install vouch-protocol
 ```
 
@@ -522,19 +549,13 @@ signer = Signer(
   did=os.environ['VOUCH_DID']
 )
 
-credential = signer.sign_credential(intent={
+credential = signer.sign(intent={
   'action': 'read_database',
   'target': 'users_table',
   'resource': 'https://api.example.com/v1/users',
 })
 # Send credential as the JSON body of the API request, content-type
-# application/vc+vouch  (legacy: application/vouch+credential+json)
-```
-
-**Legacy v0.x path (JWS, still supported):**
-```python
-token = signer.sign({'action': 'read_database', 'target': 'users'})
-# Include token in Vouch-Token header
+# application/vc+vouch
 ```
 
 ### 4. Verify (API Side)
@@ -551,7 +572,7 @@ async def protected_route(request: Request):
   credential = await request.json()
   public_key = '{"kty":"OKP", ...}' # Resolved from did:web or trusted root
 
-  is_valid, passport = Verifier.verify_credential(credential, public_key=public_key)
+  is_valid, passport = Verifier.verify(credential, public_key=public_key)
   if not is_valid:
     raise HTTPException(status_code=401, detail="Untrusted Agent")
 
@@ -562,18 +583,6 @@ async def protected_route(request: Request):
   }
 ```
 
-**Legacy v0.x path:**
-```python
-from vouch import Verifier
-
-@app.post("/api/legacy")
-def legacy_route(vouch_token: str = Header(alias="Vouch-Token")):
-  is_valid, passport = Verifier.verify(vouch_token, public_key_jwk=public_key)
-  if not is_valid:
-    raise HTTPException(status_code=401, detail="Untrusted Agent")
-  return {"status": "Verified", "agent": passport.sub}
-```
-
 **That's it.** A few lines to sign, a few to verify, on either path.
 
 ---
@@ -609,7 +618,7 @@ Works with all major AI frameworks out-of-the-box:
 
 ```python
 # Optional v1.0 profile, requires `pip install pqcrypto`
-credential = signer.sign_credential_hybrid(intent={
+credential = signer.sign_hybrid(intent={
   'action': 'submit_clinical_finding',
   'target': 'trial:NCT00000001',
   'resource': 'https://fda-submissions.example.com/api/findings',
@@ -740,7 +749,7 @@ Built by [Ramprasad Gaddam](https://www.linkedin.com/in/rampy) ([Twitter/X](http
 
 ## Contributing
 
-Contributions welcome. See [CONTRIBUTING.md](https://github.com/vouch-protocol/vouch/blob/main/CONTRIBUTING.md).
+Contributions welcome. See [CONTRIBUTING.md](https://github.com/vouch-protocol/vouch/blob/main/CONTRIBUTING.md). Looking for a place to start? Browse our [good first issues](https://github.com/vouch-protocol/vouch/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22), and open a ready-made dev environment with one click using the [Open in GitHub Codespaces](https://codespaces.new/vouch-protocol/vouch) badge above.
 
 **Areas where help is most useful:**
 - [ ] Additional framework integrations (Haystack, Semantic Kernel, LlamaIndex, others)
@@ -749,6 +758,20 @@ Contributions welcome. See [CONTRIBUTING.md](https://github.com/vouch-protocol/v
 - [ ] Independent security review and audit
 - [ ] Reference implementations in additional languages (Rust, Java, .NET)
 
+## Contributors
+
+Thanks goes to these wonderful people. This section is maintained automatically by the [all-contributors](https://allcontributors.org/) bot.
+
+<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
+<!-- ALL-CONTRIBUTORS-BADGE:END -->
+
+<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
+<!-- prettier-ignore-start -->
+<!-- markdownlint-disable -->
+<!-- markdownlint-restore -->
+<!-- prettier-ignore-end -->
+<!-- ALL-CONTRIBUTORS-LIST:END -->
+
 ---
 
 **Star this repo if you find it useful.**

{vouch_protocol-1.6.2 → vouch_protocol-2.0.1}/README.md

@@ -4,9 +4,9 @@
  <img src="docs/assets/vouch-wordmark.png" alt="Vouch Protocol" width="400">
 </p>
 
-<sub><em>Vouch Protocol™ — common-law trademark.</em></sub>
+<sub><em>Vouch Protocol™ is a common-law trademark.</em></sub>
 
-<p align="center">The Open Standard for Identity & Provenance of AI Agents</strong>
+<p align="center"><strong>The Open Standard for Identity & Provenance of AI Agents</strong>
 </p>
 
 <p align="center">
@@ -23,6 +23,10 @@
  <a href="https://discord.gg/mMqx5cG9Y"><img src="https://img.shields.io/badge/Discord-Join_Community-7289da?logo=discord&logoColor=white" alt="Discord"></a>
 </p>
 
+<p align="center">
+ <a href="https://codespaces.new/vouch-protocol/vouch"><img src="https://github.com/codespaces/badge.svg" alt="Open in GitHub Codespaces" height="28"></a>
+</p>
+
 <p align="center">
  <a href="https://github.com/vouch-protocol/vouch/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="Apache 2.0 License"></a>
 </p>
@@ -31,6 +35,16 @@
 
 ## Quick Start
 
+```bash
+# Install (Linux and macOS). On Windows, use: pip install vouch-protocol
+curl -fsSL https://vouch-protocol.com/install.sh | sh
+
+# Run vouch with no arguments and pick what you want to do
+vouch
+```
+
+Prefer to do it by hand? It is three commands:
+
 ```bash
 pip install vouch-protocol
 
@@ -41,6 +55,8 @@ vouch git init
 git commit -m "Secure commit"
 ```
 
+Setting up an agent instead of git signing? `vouch onboard --quick` generates a working identity, allow-list, verifier, and heartbeat config in one command.
+
 ---
 
 ## What's New in v1.0
@@ -53,7 +69,7 @@ Vouch Protocol v1.0 aligns directly with the open standard:
 - **Hybrid post-quantum profile** (`hybrid-eddsa-mldsa44-jcs-2026`) as an optional add-on for regulated deployments aligning with NIST CNSA 2.0 / NSM-10 timelines.
 - **Three-way cross-implementation interop** verified across Python, TypeScript, and Go.
 
-The legacy v0.x JWS API (`Signer.sign()`, `Verifier.verify()`) continues to work unchanged for a deprecation window. New code should prefer `Signer.sign_credential()` and `Verifier.verify_credential()`. See the Specification at [vouch-protocol.com/specs/SPEC/](https://vouch-protocol.com/specs/SPEC/) for the full specification.
+Credentials are issued with `Signer.sign()` and checked with `Verifier.verify()`. See the Specification at [vouch-protocol.com/specs/SPEC/](https://vouch-protocol.com/specs/SPEC/) for the full specification.
 
 ---
 
@@ -80,11 +96,13 @@ Vouch is not one tool, it is a set of them. Here is the whole map.
 - **Vouch Shield** a runtime check that inspects every tool call against your rules, like a customs officer at the door.
 - **Continuous trust** heartbeats and session vouchers, so trust is a live signal that has to be renewed, not a badge that is issued once and trusted forever.
 
-### Framework integrations (coming soon)
-Standalone packages that drop Vouch into the agent framework you already use. Each one issues a verifiable credential for a tool call, with optional delegation back to a human principal. Landing on PyPI with v1.6.2.
+### Framework integrations (new in v1.6.2)
+Standalone packages that drop Vouch into the agent framework you already use. Each one issues a verifiable credential for a tool call, with optional delegation back to a human principal.
 - **`vouch-langchain`** a LangChain tool that signs each tool call before it leaves the agent.
+- **`vouch-langgraph`** signs LangGraph tool calls and graph nodes, so a signed trail runs across the whole graph.
 - **`vouch-crewai`** a CrewAI tool, with supervisor-to-worker delegation that can only narrow authority, never widen it.
 - **`vouch-a2a`** binds an A2A (Agent2Agent) Agent Card to a Vouch identity, so two agents can verify each other before they collaborate.
+- **`vouch-goose`** registers the Vouch MCP server as an extension for Block's Goose agent, so a Goose session can sign and verify out of the box.
 - **`vouch-mlflow`** signs an MLflow model artifact at registration time, bound to a content digest so any change to the weights breaks the signature.
 - **`vouch-safetensors`** embeds a credential in a `.safetensors` header, complementary to OpenSSF Model Signing, so a model carries who produced it.
 
@@ -94,7 +112,7 @@ The standalone **`vouch-mcp`** package above ships alongside these in v1.6.2.
 Python, TypeScript, and Go are the full reference implementations. A Rust core with idiomatic Swift, JVM (Java and Kotlin), .NET, and C wrappers shares one codebase, so every language produces byte-identical output, verified against shared test vectors. A WebAssembly build is included for the browser and the edge. See the table further down for status per language.
 
 ### Robots and embodied agents
-A robot is an agent with a body, so the same primitives apply: a `did:vouch:agent` identity, delegation chains for who authorized it, and continuous trust for whether it is still behaving. Vouch adds a hardware-root-of-trust profile, so a robot's secure element (a TPM or a secure enclave) anchors its DID and signs its heartbeats, binding identity to the physical device rather than a config file. This is the open identity layer; richer robot-lifecycle tooling builds on top of it. See the open `did:vouch:agent` profile in [docs/specs/](docs/specs/).
+A robot is an agent with a body, so identity and accountability matter even more once it can cause physical harm. The `vouch.robotics` module ships six capabilities on the same `eddsa-jcs-2022` credentials as the rest of Vouch: hardware-rooted identity (bound to a TPM or secure element, so it cannot be cloned to other hardware), model and config provenance (re-signable on every OTA update), physical capability scope (force, speed, a tighter cap near humans, allowed zones, and shift windows, checked before each actuation, with narrow-only delegation), a robot-to-robot trust handshake, an encrypted tamper-evident black box with a verifiable kill switch, and a scannable offline passport. All six are implemented in Python, TypeScript, Go, and the Rust core, which flows to the Swift, Kotlin/JVM, .NET, C/C++, and WebAssembly wrappers, so a robotics credential signed in one language verifies in every other. Fourteen further capabilities round out the set: a living-trust heartbeat (a signed per-interval motion summary whose trust decays unless it is renewed in-envelope), two-level credential revocation (per-credential status lists and whole-DID kill), an accountable safety record (a tamper-evident incident ledger summarized into a portable signed record), signed perception provenance (each captured sensor frame's hash bound to the robot's key and hash-linked, so a robot can prove what its sensors saw and a substituted frame is detectable), an offline delegation lease (a short-lived, scope-bounded grant a disconnected robot verifies and acts on with no network call, nesting across vendors), a physical quorum (a cryptographic two-person rule requiring M of N attested approvers for a high-consequence action), lifecycle credentials (ownership transfer that chains into a verifiable chain of custody, key rotation that forms a key history, and a signed decommission that retires the robot), a regulatory conformance profile (a machine-checkable mapping from a robot's credentials to the clauses of ISO 10218 and 15066, the EU Machinery Regulation, the EU AI Act, and UL 3300, with a deterministic checker and a signed conformance attestation), post-quantum signing by default (robot credentials sign with the hybrid classical-plus-ML-DSA-44 cryptosuite, with backward-compatible verification, so a robot stays unforgeable across its decade-long life), and cross-embodiment identity continuity (an agent identity that moves between robot bodies, with an embodiment credential re-binding to each body's hardware root and a continuity chain that proves the same accountable agent persisted, plus a fork check), a physical custody handoff chain (a signed record of who accepted custody of a task or object at each hop across human and robot actors, so an incident traces to the exact hop and an attested condition localizes damage to the holder responsible), bounded infrastructure access (an operator-signed grant naming a resource, its permitted operations, an optional zone, and a time window, which a robot pairs with a signed request the resource authorizes offline, so a robot can open a door or dock at a charger with a tamper-evident, attributable, shrink-only record), fused-sensor provenance (a signed attestation binding a robot's fused world model to the exact set of input frame hashes and the fusion method that produced it, so a manipulated fusion result or a dropped input is detectable and every fused input traces to a frame the robot recorded), and wear and degradation attestation (a robot signs its own wear level bound to its identity and hash-linked over time, and a deterministic rule narrows its physical capability scope as it degrades, so a worn robot operates inside a tighter, verifiable envelope than the static limit it shipped with), implemented across the same languages and pinned by the shared interop vector. See [docs/robotics.md](docs/robotics.md) and the defensive disclosures PAD-064 through PAD-070, PAD-076 through PAD-084, and PAD-087 through PAD-092.
 
 ### Inside your AI tools
 - **Claude Skill**, **OpenAI Custom GPT**, and **Gemini Gem** packages that teach your AI assistant how to add Vouch to your code, running on your own AI subscription.
@@ -144,7 +162,6 @@ AI agents are making real-world API calls with **ZERO cryptographic proof** of:
 - **Human-readable JSON** (proof attaches as a sibling object, no Base64-wrapped opaque payload)
 - **Framework-agnostic** (works with MCP, LangChain, CrewAI, AutoGPT, AutoGen, Vertex AI)
 - **Cross-language interop** (Python, TypeScript, Go, byte-identical canonical form)
-- **Backward-compatible** (legacy v0.x JWS API still supported during deprecation window)
 - **Open source** (Apache 2.0 license, CC0 prior-art portfolio)
 
 **Think of it as:**
@@ -166,9 +183,9 @@ flowchart LR
   V{"✅ Verified"}
 
   P -->|"Delegation VC"| A
-  A -->|"sign_credential(intent)"| C
+  A -->|"sign(intent)"| C
   C -->|"HTTP body<br/>application/vc+vouch"| API
-  API -->|"verify_credential()"| V
+  API -->|"verify()"| V
 ```
 
 **4 Simple Steps:**
@@ -226,6 +243,10 @@ flowchart TB
 
 ### 1. Install
 ```bash
+# Linux and macOS: one line
+curl -fsSL https://vouch-protocol.com/install.sh | sh
+
+# Or with pip (any platform)
 pip install vouch-protocol
 ```
 
@@ -246,19 +267,13 @@ signer = Signer(
   did=os.environ['VOUCH_DID']
 )
 
-credential = signer.sign_credential(intent={
+credential = signer.sign(intent={
   'action': 'read_database',
   'target': 'users_table',
   'resource': 'https://api.example.com/v1/users',
 })
 # Send credential as the JSON body of the API request, content-type
-# application/vc+vouch  (legacy: application/vouch+credential+json)
-```
-
-**Legacy v0.x path (JWS, still supported):**
-```python
-token = signer.sign({'action': 'read_database', 'target': 'users'})
-# Include token in Vouch-Token header
+# application/vc+vouch
 ```
 
 ### 4. Verify (API Side)
@@ -275,7 +290,7 @@ async def protected_route(request: Request):
   credential = await request.json()
   public_key = '{"kty":"OKP", ...}' # Resolved from did:web or trusted root
 
-  is_valid, passport = Verifier.verify_credential(credential, public_key=public_key)
+  is_valid, passport = Verifier.verify(credential, public_key=public_key)
   if not is_valid:
     raise HTTPException(status_code=401, detail="Untrusted Agent")
 
@@ -286,18 +301,6 @@ async def protected_route(request: Request):
   }
 ```
 
-**Legacy v0.x path:**
-```python
-from vouch import Verifier
-
-@app.post("/api/legacy")
-def legacy_route(vouch_token: str = Header(alias="Vouch-Token")):
-  is_valid, passport = Verifier.verify(vouch_token, public_key_jwk=public_key)
-  if not is_valid:
-    raise HTTPException(status_code=401, detail="Untrusted Agent")
-  return {"status": "Verified", "agent": passport.sub}
-```
-
 **That's it.** A few lines to sign, a few to verify, on either path.
 
 ---
@@ -333,7 +336,7 @@ Works with all major AI frameworks out-of-the-box:
 
 ```python
 # Optional v1.0 profile, requires `pip install pqcrypto`
-credential = signer.sign_credential_hybrid(intent={
+credential = signer.sign_hybrid(intent={
   'action': 'submit_clinical_finding',
   'target': 'trial:NCT00000001',
   'resource': 'https://fda-submissions.example.com/api/findings',
@@ -464,7 +467,7 @@ Built by [Ramprasad Gaddam](https://www.linkedin.com/in/rampy) ([Twitter/X](http
 
 ## Contributing
 
-Contributions welcome. See [CONTRIBUTING.md](https://github.com/vouch-protocol/vouch/blob/main/CONTRIBUTING.md).
+Contributions welcome. See [CONTRIBUTING.md](https://github.com/vouch-protocol/vouch/blob/main/CONTRIBUTING.md). Looking for a place to start? Browse our [good first issues](https://github.com/vouch-protocol/vouch/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22), and open a ready-made dev environment with one click using the [Open in GitHub Codespaces](https://codespaces.new/vouch-protocol/vouch) badge above.
 
 **Areas where help is most useful:**
 - [ ] Additional framework integrations (Haystack, Semantic Kernel, LlamaIndex, others)
@@ -473,6 +476,20 @@ Contributions welcome. See [CONTRIBUTING.md](https://github.com/vouch-protocol/v
 - [ ] Independent security review and audit
 - [ ] Reference implementations in additional languages (Rust, Java, .NET)
 
+## Contributors
+
+Thanks goes to these wonderful people. This section is maintained automatically by the [all-contributors](https://allcontributors.org/) bot.
+
+<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
+<!-- ALL-CONTRIBUTORS-BADGE:END -->
+
+<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
+<!-- prettier-ignore-start -->
+<!-- markdownlint-disable -->
+<!-- markdownlint-restore -->
+<!-- prettier-ignore-end -->
+<!-- ALL-CONTRIBUTORS-LIST:END -->
+
 ---
 
 **Star this repo if you find it useful.**

{vouch_protocol-1.6.2 → vouch_protocol-2.0.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "vouch-protocol"
-version = "1.6.2"
+version = "2.0.1"
 description = "The Identity & Reputation Standard for AI Agents"
 readme = "README.md"
 requires-python = ">=3.9"
@@ -43,8 +43,10 @@ dependencies = [
 # Framework integrations
 langchain = ["langchain>=0.1.0"]
 crewai = ["crewai>=0.1.0"]
+langgraph = ["langgraph>=0.1.0"]
+goose = ["pyyaml>=6.0"]
 autogen = ["pyautogen>=0.2.0"]
-mcp = ["mcp>=1.2.0"]
+mcp = ["mcp>=0.1.0"]
 vertex = ["google-cloud-aiplatform>=1.0.0"]
 streamlit = ["streamlit>=1.0.0"]
 
@@ -71,6 +73,11 @@ azure = ["azure-keyvault-keys>=4.0.0"]
 # wrote that into a Dockerfile or requirements.txt.
 pq = []
 
+# UDNA (Universal DID-Native Addressing) identity-first transport.
+# Distribution `sirraya-udna-sdk` imports as the `udna_sdk` package.
+# Optional: when absent, the hybrid transport stack degrades to HTTP fallback.
+udna = ["sirraya-udna-sdk>=1.0.3"]
+
 # OpenTelemetry tracing
 tracing = [
     "opentelemetry-api>=1.20.0",
@@ -102,7 +109,7 @@ dev = [
 
 # All optional dependencies
 all = [
-    "vouch-protocol[langchain,crewai,autogen,mcp,vertex,streamlit,server,enterprise,tracing,dev]"
+    "vouch-protocol[langchain,crewai,langgraph,goose,autogen,mcp,vertex,streamlit,server,enterprise,tracing,dev]"
 ]
 
 [project.urls]