Security posture.
AgentEnvelope is designed so the hosted service can govern, audit, and verify public records without becoming the holder of customer authority. The same security boundary applies to agents, workers, workflows, services, devices, access grants, orders, and instructions. This page explains how to report vulnerabilities, what is in scope, and the security posture of the service as it is built.
Client-held custody
The hosted API never receives passphrases, plaintext roots, domain seeds, private keys, agent seeds, action seeds, or private capability packs.
API-keyed governance
Hosted verify and mint routes are governance services. They add ledgers, receipts, quotas, and auditability, not the base right to derive, sign, or verify offline.
Hardened web delivery
The console is served over HTTPS with security headers and a Content-Security-Policy applied per request.
Reporting a vulnerability
Please report security issues privately. Do not open a public issue for a suspected vulnerability.
Private vulnerability reporting
Use GitHub's private vulnerability reporting through the repository Security tab. Include the affected component, the impact, and steps to reproduce. Our full policy lives in the repository's SECURITY.md.
Scope and disclosure
The goal is to protect users, authority material, public records, and governed operation evidence while giving researchers a clear path for responsible reporting.
In scope
The hosted sovereign API, the authenticated console, this web application, agent-envelope-sdk, and agent-envelope-mcp.
Out of scope
Third-party infrastructure such as AWS, Amplify, and Stripe; findings requiring an already-compromised device or browser; and volumetric denial-of-service without demonstrated authority or data-integrity impact.
Policy
Good-faith research under this policy will not be pursued as a violation of our terms. There is no paid bug-bounty program at this time.
Security posture
The product boundary is deliberate: sovereign signing and offline verification do not depend on the hosted service. The portal adds API-keyed governance, ledgers, receipts, and auditability.
Custody material never leaves the client. Hosted verification receives payloads and signatures when asked to verify them, and mint routes receive signed delegates and signed mint requests. Those are governed service paths with usage controls and audit events; they are not custody of the root, domain seed, action seed, or private capability pack.
What the service stores, for how long, and the controls you hold are documented on the Trust & data handling page. AgentEnvelope does not claim any third-party compliance certification; this page describes the technical posture of the service as it is built.