Guardian documentation

Guardian reviews a mobile project on your own machine for security risk, release-compliance gaps and missing release evidence. These pages cover what it does today, how to run it, and how to read what comes back.

Where to start

Use the CLI

Confirm an installed CLI, point it at a mobile project and run a first scan end to end.

Run your first scan

Set up CI/CD

Run the release check inside your own runner, with a baseline so the gate is adoptable on an existing codebase.

CI/CD integration

Understand reports

Five report formats, who each one is for, and how to read findings alongside coverage.

Reports and formats

Review security and privacy

What Guardian reads, what never leaves your machine, and what it will never ask you for.

Security and privacy

Check the macOS release

Release verification is in progress. There is no download yet, and this page says where it stands.

Release status

All sections

Start here

Projects and platforms

Using Guardian

Reference

What the statuses mean

Guardian is a real product in active development, and these pages label every capability with one of four statuses so you can tell the difference between what runs today and what is on the way. The status appears once, on the item itself.

Status	Meaning
Verified	Proven by the CLI’s own help output or by evidence held in this repository.
Preview	Built or being built. Scope is not independently verified, so treat it as direction rather than coverage.
Planned	Not built. Always described in future tense.
Blocked	Present in the CLI, but not documented as a product capability until specific evidence exists.

The checks catalogue currently documents 14 checks: 2 verified, 6 in preview,4 planned and 2 blocked. That is the honest count, not a marketing one.