
Attestix
io.github.VibeTensor由 GitHub 帳號 VibeTensor 發布v0.5.0更新於 Nov 7, 2026
AI agent identity, signed credentials, delegated authority and governance evidence.
概覽
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。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Attestix,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
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
來源:README.md,提交 dcf823e
工具
0版本歷史
4- v0.5.0最新Oct 30, 2026
- v0.4.3Oct 12, 2026
- v0.4.2Oct 12, 2026
- v0.2.2Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分