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

# Security

> What runs where, what the Mac's owner can see, what Darkbloom keeps, and why routed jobs carry no secrets.

## Public repositories only

Your jobs run on Macs that other people own. Darkbloom checks at every job
that the repository is public and refuses private ones, so nothing a Mac sees
is secret: the code is public, the job's token is read-only, and routed jobs
cannot hold secrets.

## What runs where

Darkbloom admits only Macs enrolled to approved owners; in production they are
attested with Apple App Attest. Each job runs in a fresh virtual machine that is
removed when the job ends. On Linux the image's root is read-only and the job
writes to its own scratch disk.

## What the Mac's owner can see

Assume everything inside the job: the checked-out code, the job's environment,
its commands and output, and the files it writes. While the job runs the Mac
also holds its read-only `GITHUB_TOKEN` and the Actions runtime token, which can
read what your public repository exposes and write Actions caches and artifacts
of the run. A Mac can also alter a job's results.

Therefore:

* keep secrets in GitHub environments with protection rules (routed jobs cannot
  name an environment);
* keep releases, publishing and anything that consumes artifacts on your own
  runners;
* treat Darkbloom results like those of any third-party runner.

## Secrets

A job that references secrets (`secrets.*`, `secrets: inherit`, secrets in the
workflow's `env` or in local actions it uses), names an environment, or runs
containers is refused.

The route job itself runs on a GitHub-hosted runner and may hold secrets: it
sends Darkbloom only the repository name, the run ID and attempt, and the
lanes.

## What Darkbloom keeps

Job metadata: repository, workflow run and job IDs, commits, event and branch,
timing, outcome, runner class, the Mac that ran it and its signed receipt.
Darkbloom keeps each job's charge. Your code and logs are not
stored by Darkbloom: the job checks out your public code inside its virtual
machine, and logs go to GitHub as usual. Access requests keep the repository,
your account and the email your Darkbloom account reports.

## Receipts and integrity

The Mac that ran a job signs a receipt for it, which Darkbloom verifies.
*Verified* means the Mac's attested add-on signed it; *Unverified* means it
could not be checked (the run's result still stands). The commit also gets a
**Darkbloom sandbox integrity** check.

## GitHub App permissions

| Permission | Why |
| - | - |
| Administration: write | GitHub requires it to register a one-time (just-in-time) runner for each job Darkbloom runs |
| Actions: read | To see queued jobs and the workflow runs they belong to |
| Contents: read | To check each run's workflow files at its exact commit |
| Checks: write | To post the **Darkbloom sandbox integrity** check |
| Metadata: read | To list the installation's repositories |

It receives `workflow_job` and `repository` events.


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