Guardian keeps the analysis beside your code, makes coverage visible, and ties the release decision to the evidence behind it.
Illustrative workflow — not a live scan.
YOUR ENVIRONMENTLOCAL BY DEFAULT
Flutter, iOS or Android. Source, builds and secrets stay on your machine.
Guardian identifies the project structure it supports.
Analysis, coverage and policy evaluation, all on your own machine.
Findings are classified where they are produced.
Findings, coverage and policy decide whether the gate clears, holds for review, or blocks.
Text, JSON, SARIF, GitLab and HTML, written to the path you choose.
A local scan completes without a network connection.
OPTIONAL — REQUIRES APPROVALPlanned
Findings will be normalized, redacted and shown to you before anything moves.
Nothing will leave your environment until you approve the exact payload.
Approved, sanitized findings only — never source, builds, secrets or signing material.
Analyzers produce findings. Normalization gives them a consistent shape. Release policy weighs their severity and the coverage behind them before the report explains the result.
Run it against a project in your environment. There is no repository upload step.
Guardian identifies the platform and selects the analysis paths that apply.
Configured analyzers read local source and configuration on your machine.
Evidence, risks and checks that could not run are reported separately.
Policy exceptions are recorded with a reason rather than hidden.
The gate decision is written out with the findings, coverage and policy behind it.
These commands come from the help output of the bundled Guardian CLI. Run guardian --help against your installed build before automating anything — a newer release may differ.
guardian init
guardian detect .
guardian scan .
guardian scan . --format json --output guardian-report.json
guardian scan . --baseline guardian-baseline.json --fail-on-new
guardian release checkNo repository upload step.
The macOS application calls the Python CLI and core through a JSON boundary, which keeps the core as the single engineering source of truth. Its distribution build is still completing verification.
Release statusOptional synchronization will be disabled by default. Only normalized, redacted and explicitly approved findings will be allowed to leave the local boundary, and you will see the exact payload first.
Explore the privacy boundaryRegister interest and we will get in touch when there is a build worth your time.