Process & Scanning

Zero Branch is built for teams that need repeatable security workflows, clear ownership signals, and trustworthy outputs. This page summarizes scan workflow and scanner coverage at a practical level.

End-to-end workflow

1. Connect repository access
   You authorize repository access through approved connectors or provide a public repository URL. Access is bounded by workspace permissions.
2. Inventory repository context
   Zero Branch maps files, languages, dependency manifests, and infrastructure configuration surfaces before deeper analysis starts.
3. Execute selected scanners
   Security modules run based on plan entitlements and scan configuration, then emit normalized finding records.
4. Deduplicate and prioritize
   Findings are grouped, severity-ranked, and enriched with actionable guidance to reduce alert fatigue.
5. Publish reports and evidence
   The final report can be reviewed in-app and exported as signed evidence artifacts where available.

Scanner coverage

Feature access and throughput vary by plan. See pricing for current limits.

Security commitments

• Private repository scanning is restricted to repositories the authenticated user can access.
• Personal and organization workspaces are isolated, including connectors, repositories, scans, and reports.
• Plan limits and queue controls are enforced to protect service reliability and tenant fairness.
• Sensitive paths validate ownership, workspace context, role permissions, and callback authenticity.
• Report outputs include integrity metadata for verification workflows.

Findings are decision-support outputs and should be validated within your own threat model.

Attribution and notices