Repository navigation
client-v0.3.0 — First Functional CAGE Client SDK
·
87 commits
to main
since this release
Warning
Security Errata (2026-11-19 — GHSA-gc2v-v2jw-q499): Item 2 below overstated 0.3.0 verification coverage. In cage-client==0.3.0, ES256/EdDSA signature, expires_at, and subject.action_hash checks ran only on HTTP 200 ALLOW/NARROW envelopes — HTTP 403 DENIED (_handle_deny_response()), 202/409/422 fallback branches, and verify_verdict() did not verify envelope signatures. Upgrade to client-v0.4.0 (3feffdf6, #820, CC-04) together with a gateway that wraps HTTP 403 refusals in signed GovernanceEnvelopes.
Summary — First Functional cage-client Release
client-v0.3.0 (cage-client==0.3.0) is the first functional release of the standalone CAGE Policy Enforcement Point (PEP) client SDK (packages/cage-client/).
Required Three-Part Disclosure
client-v0.1.0andclient-v0.2.0never completed a call against a real gateway. Prior SDK releases were tested only against canned mock payloads and failed against the live CAGE Gateway wire contract (includingdefer_tokenvs.deferred_iddeferral-ticket extraction and previewGovernanceEnvelopeschema mismatches). Do not use0.1.0or0.2.0.- Envelope signature, freshness, and request-binding verification are now enforced fail-closed by default (
#675). By default (verify_signature=True,verify_expiration=True,verify_subject=True),CageClientresolves signing keys strictly out-of-band bykidvia{gateway_url}/governance/.well-known/jwks.json(JwksKeyResolverwith bounded TTL and hard staleness eviction) or caller-pinnedpublic_keys— never from embedded envelope keys — verifiesES256(EC P-256) /EdDSA(Ed25519) signatures over RFC 8785 JCS canonical bytes, enforces strict JSON parsing (rejecting duplicate keys andNaN/Infinity), validatesexpires_attemporal freshness, and checkssubject.action+subject.action_hashrequest binding before returningALLOWorNARROWverdicts (note:DENY403and202/409/422paths were NOT signature-verified in0.3.0; see Security Errata above andGHSA-gc2v-v2jw-q499). Disabling verification is rejected at startup in any non-dev/testCAGE_ENVposture. GovernanceEnvelopedroppedsubject.record_hashandgovernance_context.controls_satisfied(#676,EP-1).POST /governance/validate-actionis a non-committing (DRY_RUN) preview that neither appends a decision record nor computes control satisfaction, so both preview fields were always unpopulated and have been removed from theGovernanceEnvelopeschema (extra="forbid").
Installation
pip install https://github.com/google/cybernetic-agent-governance-engine/releases/download/client-v0.3.0/cage_client-0.3.0-py3-none-any.whl
# Or with LangGraph adapter extras from git:
pip install "cage-client[langgraph] @ git+https://github.com/google/cybernetic-agent-governance-engine.git@client-v0.3.0#subdirectory=packages/cage-client"