Attestix

io.github.VibeTensor由 GitHub 账号 VibeTensor 发布v0.5.0更新于 Nov 7, 2026

AI agent identity, signed credentials, delegated authority and governance evidence.

概览

AI 生成的概览

Attestix 让 AI 助手在本地创建签名代理身份、可验证凭证、委托授权以及 EU AI Act 治理证据。

可以做什么
  • 创建、解析、转换、验证、列出和吊销代理身份,并清除本地代理记录
  • 解析、生成和发现 A2A 代理卡片;创建与解析 did:key 和 did:web 标识符
  • 签发、验证和吊销 UCAN 风格委托令牌,并记录交互以计算信任评分
  • 建立 EU AI Act 合规档案、记录符合性评估并生成附件五声明
  • 签发与验证 W3C 可验证凭证和可验证呈现,包括来自外部来源的凭证
  • 记录训练数据来源、模型谱系和哈希链审计日志;将工件哈希锚定到 Base L2
适用场景
当你需要关于 AI 代理的可移植、加密签名的证据时适用:代理身份与能力委托、可验证凭证,或 EU AI Act 治理工作流的文档记录。适合把证明机制集成进自有应用的开发者,而非需要完整治理平台的团队。
运行要求
以本地 stdio 进程运行,需 Python(attestix 包,Python 3.11 或更高版本)。核心身份与凭证操作可离线使用本地 JSON 存储;远程 DID 解析、托管签名器和区块链锚定需要各自配置的服务。可选的 REST API 需要 ATTESTIX_API_KEY,加密密钥存储使用 ATTESTIX_KEY_PASSWORD。
安装前请注意
处于 1.0 之前的单人维护项目,尚未经过独立第三方安全审计。请保护本地签名密钥和数据目录,并在生产前测试备份恢复与所选签名后端。签名和生成的声明只是供提供方审阅的草稿,不构成法律合规。本地清除无法抹除外部副本、远程日志或已分享的凭证。区块链锚定会写入链上并产生 gas 费用。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Attestix,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Attestix]

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_complete describes recorded documentation completion. legal_conformity is not assessed; the deprecated compliant field 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.

bash
# Confirm this release is available on PyPI before installing:pip install attestix==0.5.0

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 a DeprecationWarning on first import and may be removed in a future release. Update imports to from attestix.services... import at your earliest convenience.

CLI

bash
attestix status                          # System overviewattestix init --name MyBot               # Create agent identityattestix compliance <agent-id>           # Check recorded documentation gapsattestix verify <agent-id>               # Verify identity cryptographicallyattestix audit <agent-id>                # View hash-chained audit trailattestix credential --list               # List W3C Verifiable Credentials

REST API

bash
pip install 'attestix[api]==0.5.0'# Configure ATTESTIX_API_KEY in your environment before starting the API.uvicorn attestix.api.main:app --reload   # Swagger docs at http://localhost:8000/docs

Web Dashboard

bash
pip install streamlitstreamlit run demo/webapp/app.py         # Opens at http://localhost:8501

Quick Demo

bash
python examples/quickstart.py            # Local synthetic workflow

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.

LanguageInstallStatus
Pythonpip install attestix==0.5.0PyPI 0.5.0 published; verify release files
JS / TSnpm install [email protected]npm 0.4.2; verifier source (attestix-js)
Gogo get github.com/VibeTensor/[email protected]Go module v0.4.2; verifier source (attestix-go)
Rustcargo add attestixcrates.io 0.4.1; GitHub v0.4.2 source (attestix-rs)
JavaMaven com.vibetensor:attestix:0.4.2Maven 0.4.2; verifier source (attestix-java)
RSee repository installation instructionsCRAN 0.4.1; GitHub 0.4.2 source (attestix-r)

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

ModuleWhat it does
IdentityUnified Agent Identity Tokens (UAITs) bridging MCP OAuth, A2A, DIDs, and API keys. local data erasure tooling
Agent CardsParse, generate, and discover A2A-compatible agent cards
DIDCreate and resolve W3C Decentralized Identifiers (did:key, did:web)
DelegationUCAN-style capability delegation with EdDSA-signed JWT tokens
ReputationRecency-weighted trust scoring (0.0 - 1.0) with category breakdown
ComplianceEU AI Act risk profiles, conformity assessments (Article 43), Annex V declarations
CredentialsW3C Verifiable Credentials with Ed25519Signature2020 proofs, presentations
ProvenanceTraining data provenance (Article 10), model lineage (Article 11), hash-chained audit trail (Article 12)
BlockchainAnchor artifact hashes to Base L2 via Ethereum Attestation Service, Merkle batching

Quick Start

As an MCP Server (Claude Code)

Add to your Claude Code config (~/.claude.json):

json
{  "mcpServers": {    "attestix": {      "type": "stdio",      "command": "python",      "args": ["-m", "attestix.main"]    }  }}

Then ask Claude:

"Create an identity for my data analysis agent with capabilities: data_analysis, reporting"

As a Python Library

python
from attestix.services.identity_service import IdentityServicefrom attestix.services.compliance_service import ComplianceServicefrom attestix.services.credential_service import CredentialService
identity_svc = IdentityService()compliance_svc = ComplianceService()credential_svc = CredentialService()
# 1. Create an agent identityagent = identity_svc.create_identity(    display_name="MyAgent",    source_protocol="manual",    capabilities=["data_analysis", "reporting"],    description="Analyzes quarterly financial data",    issuer_name="VibeTensor",    expiry_days=365,)agent_id = agent["agent_id"]      # attestix:f9bdb7a94ccb40f1agent_did = agent["issuer"]["did"]  # did:key:z6Mk...
# 2. Create a compliance profileprofile = compliance_svc.create_compliance_profile(    agent_id=agent_id,    risk_category="limited",    provider_name="VibeTensor",    intended_purpose="Analyzes quarterly financial data",)
# 3. Issue a verifiable credentialcredential = credential_svc.issue_credential(    subject_id=agent_id,    credential_type="AgentIdentityCredential",    issuer_name="VibeTensor",    claims={"capabilities": ["data_analysis", "reporting"]},    expiry_days=365,)print(credential["proof"]["type"])  # Ed25519Signature2020

For a complete end-to-end walkthrough covering all 9 modules, run the quickstart:

bash
python examples/quickstart.py

From Source

bash
git clone https://github.com/VibeTensor/attestix.gitcd attestixpip install -r requirements.txtpython -m attestix.main

AI governance evidence workflow

Record a high-risk AI agent documentation workflow for provider review:

1. create_agent_identity        --> UAIT with DID (Ed25519 signed)2. record_training_data         --> Article 10 data governance3. record_model_lineage         --> Article 11 technical documentation4. create_compliance_profile    --> Risk categorization + obligations5. record_conformity_assessment --> Operator-recorded assessment details6. generate_declaration_of_conformity --> Annex V declaration + W3C VC7. create_verifiable_presentation     --> Signed VP for a verifier with a fresh challenge

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:

record_conformity_assessment(assessment_type="self", ...)--> ERROR: "High-risk AI systems require third_party conformity assessment"

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:

ArtifactStandardSigned
Agent Identity (UAIT)Custom + DIDEd25519
Verifiable CredentialW3C VC Data Model 1.1Ed25519Signature2020
Verifiable PresentationW3C VPEd25519Signature2020
Delegation TokenUCAN-style JWTEdDSA
Draft evidence credentialAttestix documentation profileEd25519
Audit TrailHash-chained logSHA-256 chain
Blockchain AnchorEAS on Base L2On-chain

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

attestix/                  # Canonical Python package  main.py                  # MCP server entry point (MCP tools)  cli.py                   # `attestix` console script  config.py                # Environment-based configuration  errors.py                # Error handling with JSON logging  api/                     # FastAPI REST surface    main.py                # uvicorn entry: `attestix.api.main:app`    routers/               # REST routers  auth/    crypto.py              # Ed25519 key management    ssrf.py                # SSRF protection for outbound HTTP  services/    identity_service.py    # UAIT lifecycle, local data erasure    agent_card_service.py  # A2A agent card operations    did_service.py         # DID creation and resolution    delegation_service.py  # UCAN delegation tokens    reputation_service.py  # Trust scoring    compliance_service.py  # Operator-recorded profiles and assessment evidence    credential_service.py  # W3C VCs and VPs    provenance_service.py  # Training data, lineage, audit trail    blockchain_service.py  # Base L2 anchoring via EAS  storage/                 # Repository seam (file / memory / pg)  signing/                 # Signer seam (in-process / kms)  audit/                   # Tamper-evident event chain  tenancy/                 # Tenant context  idempotency/             # Stripe-style idempotency keys + middleware  blockchain/    merkle.py              # Merkle tree for batch anchoring  tools/                   # MCP tool definitions (one file per module)

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
ToolDescription
create_agent_identityCreate a UAIT from any identity source
resolve_identityAuto-detect token type and register
verify_identityCheck existence, revocation, expiry, signature
translate_identityConvert to A2A, DID Document, OAuth, or summary
list_identitiesList UAITs with protocol/revocation filters
get_identityGet full UAIT details
revoke_identityMark a UAIT as revoked
purge_agent_dataRemove locally managed records and parseable local backups; external copies need separate handling
Agent Cards
ToolDescription
parse_agent_cardParse an A2A Agent Card JSON
generate_agent_cardGenerate agent.json for hosting
discover_agentFetch /.well-known/agent.json from a URL
DID
ToolDescription
create_did_keyGenerate ephemeral did:key with Ed25519 keypair
create_did_webGenerate did:web DID Document for self-hosting
resolve_didResolve any DID to its DID Document
Delegation
ToolDescription
create_delegationUCAN-style capability delegation token
verify_delegationVerify JWT signature, expiry, structure
list_delegationsList delegations by agent and role
revoke_delegationRevoke a delegation token
Reputation
ToolDescription
record_interactionRecord outcome and update trust score
get_reputationGet score with category breakdown
query_reputationSearch agents by reputation criteria
Compliance
ToolDescription
create_compliance_profileCreate EU AI Act profile with risk categorization
get_compliance_profileRetrieve full compliance profile
update_compliance_profileUpdate an existing compliance profile
get_compliance_statusGap analysis: completed vs missing requirements
record_conformity_assessmentRecord self or third-party assessment (Article 43)
generate_declaration_of_conformityGenerate Annex V declaration + auto-issue VC
list_compliance_profilesFilter by risk category and compliance status
Credentials
ToolDescription
issue_credentialIssue W3C VC with Ed25519Signature2020 proof
verify_credentialCheck signature, expiry, revocation
verify_credential_externalVerify any VC JSON from an external source
revoke_credentialRevoke a Verifiable Credential
get_credentialGet full VC details
list_credentialsFilter by agent, type, validity
create_verifiable_presentationBundle VCs into a signed VP for a verifier
verify_presentationVerify a VP with embedded credentials
Provenance
ToolDescription
record_training_dataRecord training data source (Article 10)
record_model_lineageRecord model chain and metrics (Article 11)
log_actionLog agent action with hash-chained audit trail (Article 12)
get_provenanceGet full provenance record
get_audit_trailQuery audit log with filters
Blockchain
ToolDescription
anchor_identityAnchor identity hash to Base L2 via EAS
anchor_credentialAnchor credential hash to Base L2 via EAS
anchor_audit_batchMerkle batch anchor of audit log entries
verify_anchorVerify an on-chain anchor against local data
get_anchor_statusGet anchoring status for an artifact
estimate_anchor_costEstimate gas cost for anchoring

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:

bash
docker build -f Dockerfile.test -t attestix-bench . && docker run --rm attestix-bench
StandardWhat is testedTests
RFC 8032 (Ed25519)4 IETF canonical vectors: key derivation, signature generation (exact match), verification, tamper rejection18
W3C VC Data Model 1.1Credential structure, Ed25519Signature2020 proof, mutable field exclusion, VP structure, replay protection25
W3C DID Core 1.0did:key and did:web document structure, roundtrip resolution, Ed25519VerificationKey202018
UCAN v0.9.0JWT header (alg/typ/ucv), all payload fields, capability attenuation, expiry enforcement, revocation18
MCP ProtocolMCP tools registered, 9 modules, async convention, snake_case naming5
PerformanceEd25519 key gen, JSON canonicalization, sign/verify, identity creation, credential ops7

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_PASSWORD is 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:

bibtex
@article{dubasi2026attestix,  title     = {Attestix: A Unified Attestation Infrastructure for Autonomous AI Agents},  author    = {Dubasi, Pavan Kumar},  year      = {2026},  url       = {https://github.com/VibeTensor/attestix},  note      = {Open-source. Apache License 2.0}}

Documentation

Full documentation at attestix.io/docs

GuideDescription
Getting StartedInstallation and first identity in 5 minutes
EU AI Act ComplianceStep-by-step compliance workflow
Risk ClassificationHow to determine your AI system's risk category
ArchitectureSystem design and data flows
API ReferenceMCP tools with parameter tables
Integration GuideLangChain, OpenAI Agents SDK, CrewAI, MCP client
ConfigurationEnvironment variables, storage, Docker
Research PaperPaper, citation formats, evaluation highlights
Reputation ScoringRecency-weighted trust scoring and categories
ExamplesEnd-to-end code examples for common workflows

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.

[GitHub Sponsors]


Contributing

See CONTRIBUTING.md for development setup and guidelines.

License

Apache License 2.0. See LICENSE.


[Attestix]

Built by VibeTensor

来源:README.md,提交 dcf823e

工具

0
SourceWeft 曾在隔离沙箱中以无凭据方式启动该软件包一次,以列出其工具,但未能完成:服务器未能启动。

版本历史

4
  1. v0.5.0最新Oct 30, 2026
  2. v0.4.3Oct 12, 2026
  3. v0.4.2Oct 12, 2026
  4. v0.2.2Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分