Security and privacy
A transferred package is untrusted content, whoever sent it. ACT never transfers credentials, private conversations, agent memory, or system instructions. Packages are limited to inspectable text formats; scripts and binaries are rejected. Outbound packages are scanned for common secret patterns, and a likely credential blocks the export until the sender removes it.
Automated scans have limits. A scan that passes means no known pattern matched; it is not a promise that a package is safe. Verification runs use synthetic inputs and fixed fixtures, with no real credentials and no open network access. Read the threat model in the project documentation for the full list of what ACT does and does not protect against.
Package contents are never sent to analytics services, and invitation tokens are stored only as hashes. Revoking a transfer stops future access to the hosted copy; it cannot recall copies a recipient has already downloaded, and the product says so at the point of revocation.
Limits, stated plainly
Secret and policy scans search for known patterns. A scan with no findings means no known pattern matched; it does not prove a package is safe, and no receipt label in ACT states that a capability is safe in general.
Verification covers the checks listed on the receipt for one package digest, one test suite, and one environment: structural, security policy, compatibility, and the behavioral cases that ran. Checks listed as missing or not tested did not run, and the receipt says which ones they were. Verification covers those checks and no others.
An invitation link works as a bearer link until the transfer is received: anyone who holds the link can read the offer metadata (sender, capability name, description) and, if the offer names no recipient email, receive the transfer after signing in. Treat the link like a credential. Naming a recipient email binds receiving to that account. Invitations expire, and the sender can revoke a transfer at any point before acceptance.
A share link works the same way, with a wider summary page: anyone holding the link can read the capability name and description, the manifest summary, declared dependencies and requested permissions, the security findings summary, and the package file list (names and sizes) until the link is claimed, expires (7 days), or is revoked. Package contents are never shown before a claim. After a claim, the link shows only the capability name and the claimed status, and the package is served only to the claimant. Treat a share link like a password-reset link: whoever gets it first can claim it. Only the SHA-256 hash of the link token is stored, link pages send Referrer-Policy: no-referrer, and tokens never appear in logs or audit events.
See the privacy page for what the service stores and how deletion works.