The atelier CLI and Manager GUI drive the Docker appliance that runs people's websites — install, update, back up, restore. A vulnerability here can affect real sites, so we take security reports seriously. Thank you for helping keep Atelier safe.

Please do not report security issues in public GitHub issues, pull requests, or discussions.

Report privately through GitHub's private vulnerability reporting:

1. Go to the Security tab of this repository.
2. Click Report a vulnerability.
3. Fill in the advisory form.

This opens a private channel visible only to you and the maintainers. A good report includes:

• The version (atelier --version) and how you installed it (Homebrew, direct download).
• Your OS and architecture.
• A clear description of the issue and its impact.
• Steps to reproduce, ideally with a minimal proof of concept.

• Acknowledgement within 3 business days.
• An initial assessment (severity, reproducibility, rough timeline) within 7 business days.
• Regular updates, and credit in the advisory and release notes when the fix ships, unless you'd prefer to stay anonymous.

We follow coordinated disclosure: we agree a disclosure date with you, publish a GitHub Security Advisory when the fix is available, and ask that details stay private until then.

The manager follows Semantic Versioning and is released through GitHub Releases and the aincient-labs/homebrew-tap. Security fixes ship in a new release; the latest release is the supported version. Update with brew upgrade atelier or by downloading the newest release.

Signing status by platform:

• macOS builds are Developer ID signed and notarized by Apple. macOS verifies the signature on first launch; if a build fails Gatekeeper verification, don't run it — open a security report instead.
• Windows builds are not signed yet. Authenticode signing (via the SignPath Foundation) is a planned fast-follow. Until then, SmartScreen will warn on first launch; verify a download against its published .sha256 checksum before running it.

Anything in this repository is in scope: the CLI, the Tauri GUI, and the shared aincient-core Rust crate that drives the Docker lifecycle. Issues in the CMS appliance itself (the container image, operator console, or modules) belong in the atelier-cms security channel.

Thank you for helping keep Atelier and the sites it runs safe.