Do not open a public GitHub issue. Use one of the following private channels, in preference order:

1. Preferred — file a private advisory through GitHub Security Advisories. This keeps the report attached to the affected repository and lets us collaborate on a fix without disclosure.
2. Email — write to security@aphrody.dev. Use the PGP key below if you need transport encryption.

Include a minimal reproducer, the affected commit hash, and the platform (Linux / Windows / wasm) you observed the issue on.

• Initial acknowledgement: within 48 hours (best-effort within 1 week for off-hours weekends or holidays).
• Triage decision: within 5 business days.
• Coordinated disclosure window: 30 days from acknowledgement, unless mutually extended (high-severity supply-chain issues may require longer).

In scope:

• The published aphrody binary and the published crates under the aphrody-code/* namespace.
• The A2A protocol surface (ai.json manifest, .coord mailbox listener, envelope schema) shipped from this repository.
• Supply-chain integrity of declared dependencies (Cargo.lock, bun.lock).
• Credential or token leakage in repository content or release artifacts.

Out of scope:

• Vendored upstreams under vendor/ (Bun fork, Electron prebuilt) — report directly to their respective upstream projects.
• Archived crates listed in CLAUDE.md (google_os, bun_ffi, python_ffi, google_kv, n2b legacy) — they are no longer built or distributed.
• Deprecated branches (anything not listed as Yes / Best-effort above).
• Social-engineering, physical access, or denial-of-service via brute force against third-party infrastructure.
• Self-hosted infrastructure (VPS, A2A peer at C:\winclean\) — those are operator-specific and out of repository scope.

We will not pursue legal action against good-faith security research that:

• Respects the disclosure window above.
• Does not access, modify, or exfiltrate data belonging to other users.
• Does not degrade service for other users.

If in doubt, ask first via security@aphrody.dev — we would rather clarify scope than discourage a report.

A PGP key for security@aphrody.dev will be published at https://aphrody.dev/.well-known/pgp-key.txt — pending publication. Until then, GitHub Security Advisories provide an equivalent confidential channel.

Researchers who responsibly disclose are credited in the release notes of the patched version (and in the relevant GitHub Security Advisory), unless they request to remain anonymous.