Skip to main content

✅ FINAL COMPLIANCE VERDICT

A2A Core Concept Status
Tasks ✅
Task lifecycle ✅
Parts ✅
Artifacts ✅
Artifact streaming ✅
Discovery ✅
AgentCard ✅
Webhooks / Push ✅
Context ✅
Security hooks ✅
Conformance tests ✅

5️⃣ FINAL COMPLIANCE VERDICT (NO AMBIGUITY)

A2A Discovery Requirement Status
Agent Card ✅
Well-known discovery ✅
Direct discovery ✅
Secure discovery ✅
Capability introspection ✅
Registry discovery ✅
Trust declaration ✅
Selective disclosure support ✅
Spec-level tests ✅

🧠 Enterprise Coverage: Now Fully Completed

Enterprise Requirement SDK Status Covered by
Security & Trust ✅ security/ + trust declarations
Auth / Scopes ✅ security/ + enterprise/auth_helpers.py
RBAC ✅ enterprise/rbac.py
Audit ✅ enterprise/audit.py
Policy Enforcement ✅ enterprise/policy_engine.py
HITL support ✅ enterprise/hitl.py
mTLS enforcement ✅ enterprise/auth_helpers.py
Message governance ✅ Governance in schema

✅ Final Compliance Checklist (Life of a Task)

Spec Requirement Covered Notes
Stateless message responses ✅ Done
Stateful task initiation ✅ Done
Task lifecycle updates ✅ Done
Context grouping (contextId) ✅ Done
Immutable tasks ✅ Done
Parallel follow-ups ✅ Done
Artifact linkage ✅ Done
Reference task refinements ⚠ Partial Needs reference_task_ids
Task event models ⚠ Partial Needs explicit event types

🧠 SPEC COMPLIANCE CHECKLIST (Extensions)

Extension Feature Implemented? Location
Declare extensions in AgentCard ✔ schema/agent_card.py
Extension model (uri, params, required) ✔ extensions/models.py
Client negotiation helper ✔ extensions/negotiation.py
Transport support for headers ✔ transport/extension_headers.py
Server echo back activated extensions ✔ extensions/activation.py
Tests for extension behaviors ✔ tests_conformance/*.py
Input validation guidance ✔ extension params should be validated in extension code
Required extension enforcement ✔ (model field exists) enforcement logic TBD in server layer

✅ What This Validator Guarantees (Spec-Level)

Requirement Status
Valid URI enforcement ✅
Required extension enforcement ✅
Unsupported extension rejection ✅
Dependency validation ✅
Parameter schema enforcement ✅
Duplicate detection ✅
Safe for enterprise use ✅
Framework-agnostic ✅

🎯 Final Compliance Checklist — Streaming & Async

Spec Requirement Covered?
Async accept (202) ✅
Correlation IDs ✅
Polling API ✅
Push webhooks ⚠ via enterprise module
Streaming parts (structured) ✅
SSE streaming ✅
WebSocket streaming ✅
Backpressure / generator ✅
Completion semantic ✅
Error handling in streams ⚠ basic

Metadata

Release files for a2a-python-sdk 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for a2a-python-sdk 0.1.6
File Size Uploaded Provenance Actions
a2a_python_sdk-0.1.6.tar.gz 34.4 kB Without provenance Details for a2a_python_sdk-0.1.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for a2a-python-sdk 0.1.6
File Interpreter ABI Platform Actions
a2a_python_sdk-0.1.6-py3-none-any.whl Python 3 none any Details for a2a_python_sdk-0.1.6-py3-none-any.whl

Total release size: 91.0 kB

Release files / a2a_python_sdk-0.1.6.tar.gz

Download URL a2a_python_sdk-0.1.6.tar.gz
Size 34.4 kB
Tags Source
SHA-256 checksum
How to use checksums
4b4091092ea7567ea9d64c12c13080e8a7ef3ea20a74c15758eb3b5f80f6fed1
BLAKE2b-256 checksum
How to use checksums
6241283c6c281f9c7affd5255837a8842f95742d7029a4cc104b4d5adc40dc80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.14

Release files / a2a_python_sdk-0.1.6-py3-none-any.whl

Download URL a2a_python_sdk-0.1.6-py3-none-any.whl
Size 56.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0b7c865bf406fdf994ab1f4d47a258ed142c848962bd78c3da5fb5d47a96dce3
BLAKE2b-256 checksum
How to use checksums
2057b497cad2d16496e12891d28af65fa90fe1b782a98cdda74328c2feeb929a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.14

Security for a2a-python-sdk 0.1.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.6 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page