
Attestix
io.github.VibeTensorPublished by GitHub account VibeTensorv0.5.0Updated Nov 7, 2026
AI agent identity, signed credentials, delegated authority and governance evidence.
Overview
Attestix gives an AI assistant tools to create signed agent identities, verifiable credentials, delegations and EU AI Act governance evidence locally.
- What you can do
- Create, resolve, translate, verify, list and revoke agent identities, and purge local agent records
- Parse, generate and discover A2A agent cards; create and resolve did:key and did:web identifiers
- Issue, verify and revoke UCAN-style delegation tokens, and record interactions to compute trust scores
- Build EU AI Act compliance profiles, record conformity assessments and generate Annex V declarations
- Issue and verify W3C verifiable credentials and presentations, including credentials from external sources
- Record training data provenance, model lineage and hash-chained audit logs; anchor artifact hashes to Base L2
- When to use it
- Useful when you need portable, cryptographically signed evidence about AI agents: agent identity and capability delegation, verifiable credentials, or documentation trails for EU AI Act governance workflows. It suits developers building attestation into their own applications rather than teams wanting a full governance platform.
- Requirements
- Runs as a local stdio process started with Python (the attestix package, Python 3.11 or later). Core identity and credential operations work offline with local JSON storage; remote DID resolution, hosted signers and blockchain anchoring need their configured services. The optional REST API requires an ATTESTIX_API_KEY, and encrypted key storage uses ATTESTIX_KEY_PASSWORD.
Installation
In SourceWeft
- Open Attestix in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Attestix
Signed identity and evidence for AI agents
[CI] [Lint] [Security] [Coverage] [PyPI] [Python] [License] [Docs] [Website]
Record cryptographically verifiable evidence to support AI governance workflows.
Open-source identity, credentials, compliance automation, and trust scoring.
MCP and REST interfaces,
Automated functional tests and Attestix interoperability benchmarks.
Real integrations with LangChain, OpenAI Agents SDK, and CrewAI.
Status: pre-1.0 toolkit; this README describes current main source. Single-maintainer project, community contributions welcome. No independent third-party security audit has been performed yet; deploy with the same diligence you would apply to any pre-1.0 open-source crypto stack.
Source and verification status
Python attestix 0.5.0 is published on PyPI and requires Python 3.11 or later. Confirm the release files on PyPI before installing; source metadata alone is not proof of publication. Python 0.4.3 is a previously published release with the Filelock constraint described below. Language SDKs have independent release schedules; verify each registry and pin the version you reviewed.
- Credential verification binds the stated issuer to the supported proof controller. Ambiguous NFC-normalized keys fail before signing or verification.
- Presentation verification requires the caller's expected challenge and domain. A signature alone does not provide replay protection.
- REST use requires an API key by default. The default REST server is single-tenant and rejects non-default tenant headers; a shared API key does not provide cross-tenant authorization.
- JSON updates use the shared storage lock. Protect the local signing key and data directory; test backup restoration, isolation and your selected signer/backend before production.
workflow_completedescribes recorded documentation completion.legal_conformityis not assessed; the deprecatedcompliantfield is a workflow alias. Generated declarations are drafts for provider review.- Local purge cannot erase external replicas, remote logs, previously shared credentials or third-party backups. Plan historical data and credential migration separately.
Install
Attestix 0.5.0 requires Python 3.11 or later for the patched file-locking dependency. Earlier releases retain their own Python requirements; check the registry files for the version you install.
Version 0.4.3 requires filelock<4.0.0 and cannot install patched Filelock 4.2.1. On Unix, keep the Attestix data directory private and prevent other users from replacing its lock path. This limits the conditional local file-truncation risk described in the Filelock advisory. Moving from 0.4.3 to 0.5.0 requires Python 3.11 or later; review the release files before upgrading.
Since 0.4.0, the supported namespace is the canonical
attestix.*namespace. The older flat layout (from services... import,from auth... import, ...) keeps working via thin deprecation shims that emit aDeprecationWarningon first import and may be removed in a future release. Update imports tofrom attestix.services... importat your earliest convenience.
CLI
REST API
Web Dashboard
Quick Demo
Verify in any language
Attestix credentials use a published canonical-JSON and Ed25519 verification profile. Language-specific verifier repositories share conformance fixtures, but their trust-input and delegation-chain checks differ. Read each verifier README and pin a reviewed version. Cryptographic validity is separate from issuer trust, authorization, revocation and replay policy.
Every verifier targets the Attestix canonical-JSON profile, which differs from strict RFC 8785,
and Ed25519 signatures (RFC 8032) against
the shared spec/verify/v1
vectors. Verify in the browser at https://attestix.io/verify, or read the
bundle wire-format at https://attestix.io/spec/bundle/v1.
Why Attestix
The EU AI Act has a staged application timeline. The European Commission currently lists 2 December 2027 for specified high-risk use cases and 2 August 2028 for high-risk systems embedded in regulated products. Applicability depends on the system and the operator's role. See the European Commission's current AI Act guidance.
Attestix helps organize evidence; a signature or generated declaration does not establish legal conformity or replace the applicable assessment process.
Attestix provides agent identity, signed credentials, delegation, and offline verification for developers who need portable evidence in their applications. Broader governance platforms also offer APIs, SDKs, agent governance, and compliance workflows; evaluate their current capabilities against your requirements.
Agent identity is fragmenting across walled gardens (Microsoft Entra, AWS AgentCore, ERC-8004). Attestix combines agent identity, AI governance evidence and verifiable credentials in one toolkit.
Attestix fills this gap.
Modules
Quick Start
As an MCP Server (Claude Code)
Add to your Claude Code config (~/.claude.json):
Then ask Claude:
"Create an identity for my data analysis agent with capabilities: data_analysis, reporting"
As a Python Library
For a complete end-to-end walkthrough covering all 9 modules, run the quickstart:
From Source
AI governance evidence workflow
Record a high-risk AI agent documentation workflow for provider review:
The current Attestix workflow blocks self-assessment for a profile marked high-risk. This application policy is not a universal determination of the legally applicable assessment route:
Full walkthrough: EU AI Act Compliance Guide
How It Works
Credentials and presentations carry signatures; audit chains carry integrity hashes. Not every record or external artifact is independently signed:
Local operation. Core identity and credential operations can use local JSON storage. Remote DID resolution, hosted signers and blockchain integrations require their configured services.
Architecture
The pre-v0.4.0 flat layout (services/, auth/, storage/, ...) is
preserved as deprecation shims at the same paths. They re-export from the
canonical attestix.* namespace and emit a DeprecationWarning on first
import. The shims are deprecated and retained in 0.5.0.
MCP tools
Identity
Agent Cards
DID
Delegation
Reputation
Compliance
Credentials
Provenance
Blockchain
Standards Conformance
Public tests and conformance fixtures cover selected signature, canonicalization, credential, delegation and interface behavior. They do not establish universal W3C interoperability, legal conformity, certification or operating acceptance. Consult the test cases and the selected verifier's documented boundaries. Run them yourself:
Performance
Benchmark results depend on interpreter, hardware, storage and workload. Run the repository benchmarks on your target environment; no static latency figure here is an operating guarantee.
Security
- Ed25519 signatures on all UAITs, VCs, assessments, declarations, and audit entries
- Hash-chained audit trail with SHA-256 for tamper-evident logging
- SSRF protection blocks private IPs, metadata endpoints, and DNS rebinding
- Encrypted key storage with AES-256-GCM when
ATTESTIX_KEY_PASSWORDis set - Private keys never exposed in tool responses
- No external API calls required for core operations
Research Paper
Attestix is described in a research paper covering system architecture, cryptographic pipeline, governance evidence workflows, and evaluation with 531 automated tests (440 functional + 91 RFC / W3C conformance benchmarks).
Attestix: A Unified Attestation Infrastructure for Autonomous AI Agents Pavan Kumar Dubasi, VibeTensor Private Limited, 2026.
Citing Attestix
If you use Attestix in your research, please cite:
Documentation
Full documentation at attestix.io/docs
Disclaimer
Attestix generates machine-readable, cryptographically signed compliance documentation. It is a documentation and evidence tooling system. It does not replace legal counsel, notified body assessments, or official regulatory submissions. Always consult qualified legal professionals for compliance decisions.
Sponsors
Attestix is free and open-source. If you or your organization benefit from it, please consider sponsoring to support continued development, security audits, and infrastructure.
Contributing
See CONTRIBUTING.md for development setup and guidelines.
License
Apache License 2.0. See LICENSE.
Built by VibeTensor
Source: README.md at commit dcf823e
Tools
0Version history
4- v0.5.0LatestOct 30, 2026
- v0.4.3Oct 12, 2026
- v0.4.2Oct 12, 2026
- v0.2.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts