Please report security issues privately — do not open a public issue.

Use GitHub's private vulnerability reporting (repository Security tab → Report a vulnerability). Expect an acknowledgement within 72 hours and a coordinated disclosure once a fix is available.

ycli reads YANDEX_ID_OAUTH_TOKEN and YANDEX_ID_ORGANIZATION_ID from the environment (via Credentials() at the composition root) and sends them only to the official Yandex 360 API endpoints — never logged, never written to disk, never transmitted elsewhere.

In scope:

• Credential handling and accidental token/PII leakage (logs, error output, the demo shims).
• The MCP annotation-honesty boundary — the MCP server is read/write, and every tool's annotations must be honest (reads carry readOnlyHint; writes carry explicit destructiveHint / idempotentHint and the write tag). ycli mcp start --read-only must expose no write tools — a write tool leaking through that flag is in scope.
• Dependency or supply-chain issues in the published yandex-cli distribution.

Out of scope: vulnerabilities in the Yandex 360 services themselves (report those to Yandex), and issues that require a pre-compromised local environment.

Security fixes target the latest released 0.x line on PyPI (yandex-cli). Pin to a recent version and upgrade promptly.