Security boundary

Verify the boundary before you trust it.

Phantom addresses one hard problem: letting a supported agent workflow use configured API credentials without placing provider values in the managed dotenv context. The security case is open to inspection, and its limits are part of the product contract.

What the shipped local path does

A smaller credential surface for agent-driven work.

01

Value-blind managed path

Managed dotenv files contain phantom placeholders. On an exact configured route, the authenticated loopback proxy injects the route's vault value into its fixed authentication header.

02

Local-first custody

The shipped path stores credentials through an OS keychain or encrypted-file backend. Cloud and team source does not prove a commissioned hosted service.

03

Explicitly narrow protection

Phantom reduces accidental credential exposure in its managed workflow. It is not a sandbox, endpoint-security suite, identity provider, or regulatory certification.

Known limits are review inputs.

These summaries do not replace the versioned threat model. Review the exact installed artifact, configuration, endpoint, and client before adoption.

  • Equivalent same-user shell, debugger, filesystem, or terminal-control authority can defeat the separation.
  • A compromised operating system, administrator, replaced binary, or malicious dependency remains outside the boundary.
  • Audit evidence is local by default and is not an independently signed or centrally retained record.
  • Provider issuance and lifecycle operations are hard-denied in 0.7.8; source adapters and test mocks are not live integrations.
  • Independent binary signatures, macOS notarization, Windows Authenticode, and regulatory certifications are not claimed.

Evidence, not badges

Start your review in the canonical sources.

Phantom has no paid bug bounty and claims no certification or independent security audit. Report suspected vulnerabilities privately; do not include real credentials or personal data.