> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bach builds Windows installers from one bach.toml with the bach command: bach init, bach check, bach preview, bach build. Installs are per user and need no administrator rights by default. installer.scope = "machine" installs for every user after one Windows prompt. On Windows, run setup files with Start-Process -Wait -PassThru in PowerShell, and give signtool arguments that start with the word sign.

# Bach security policy: report a vulnerability

> How to report a security problem in Bach privately, which versions get fixes, and what counts as a vulnerability and what does not.

Bach writes installers that other people run on their computers, so a security bug can reach a lot of machines. Reports are welcome and taken seriously. This page summarizes the policy; the full text is in [SECURITY.md](https://github.com/usebach/bach/blob/main/SECURITY.md).

## Report a problem

> [!WARNING]
>
> Do not open a public issue or pull request for a security problem.

Use GitHub's private form: [Report a vulnerability](https://github.com/usebach/bach/security/advisories/new). Only the maintainers can see the report. Include what you can:

* What the problem is and which part of Bach it touches (`bach`, `bach-setup`, the install scripts, the GitHub Action).
* The version or commit, and your Windows version if it matters.
* Steps to reproduce, ideally a small `bach.toml` or a crafted setup file.
* What an attacker gains, for example "writes a file outside the install folder".

You get an answer within a few days. The maintainers confirm the problem, work on a fix with you, and publish an advisory and a release. Reporters are credited if they want it. Please give reasonable time to ship the fix before you disclose details.

## Supported versions

Bach is early. Only the latest release and `main` get security fixes. Setup files you built with an older Bach keep the runtime they were built with, so after a fix ships, rebuild and re-release your setup file with the new `bach`.

## What counts

Bach's [safety rules](/docs/concepts/safety.md) are promises. Breaking one is a vulnerability, for example:

* A setup file that writes, replaces or deletes anything outside its install folder or the data folders the user opted into.
* An uninstaller or update that removes files it did not install.
* Setup asking for or gaining administrator rights the app did not ask for (`installer.scope = "machine"`, `elevated = true`), running a program from a place the user's own programs can write with those rights, or writing outside the user's own folders and `HKCU` (or the machine-wide places a machine-wide app uses).
* Changing or deleting registry keys, `PATH` entries, link schemes or file types that belong to another program.
* A damaged payload, manifest or feed that is accepted, or a self-update that installs a file that does not match the feed's SHA-256 or the app's id, or that downloads over http.
* Memory-safety bugs or crashes triggered by an untrusted setup file.
* `install.ps1`, `install.sh` or `action.yml` running or replacing something the user did not ask for.

## What does not

* A developer putting something harmful into their own `bach.toml` or app files.
* Unsigned setup files triggering SmartScreen.
* The unsigned `uninstall.exe` an install leaves behind.
* Problems that need an attacker who already runs code as the same user.
* Findings in a dependency that Bach does not use in a reachable way. If unsure, report it anyway.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.