Security and privacy

Source processing

Normal graph and practice analysis run locally. This public website has no connection to your local graph and does not receive your repository content.

Command execution

Verification, mutation testing, and historical replay can execute repository code. Copies and checkouts protect a working tree but do not sandbox a malicious program. Use trusted repositories and appropriate isolation.

Private service operation

The CLI defaults to loopback. Bearer authentication, request limits, and readiness probes support controlled private operation. Authentication is shared across projects in a server; there is no per-tenant isolation.

Policies and secrets

Approval hashes detect local policy edits but are not identity or role-based authorization. Keep credentials outside source files and preserve access controls on local state. Back up approved policies, baselines, and durable histories.

External model calls

Only explicitly configured provider features transmit model inputs. Treat retrieved and generated content as untrusted, review provider retention, and constrain tool permissions.

Reporting an issue

Share a minimal sanitized reproduction privately with the project maintainer through an established private contact. Do not publish credentials or proprietary graph data.