Inspect selected changes at verified commits.
Review selected files from a connected GitHub pull request with bounded static and syntax checks. Keep the verified base and head commits, findings, and coverage together.
- Authenticated pull request metadata and immutable base/head commits
- Fixed static patterns and supported syntax parsing
- Selected-file hashes, coverage, and skipped checks
- A selected-scope policy decision at your severity threshold
A report with clear boundaries.
Each report lists the checks performed, the resources reached, and any checks skipped. Findings include observed or heuristic confidence so you can judge the evidence.
- Sign-in and a current encrypted connection to the selected repository are required for every run.
- Select from a pull request with at most 50 changed files. Unselected and unsupported files remain untested.
- Builds, project tests, dependency installation, API requests, and browser flows are not executed. Customer commands are not accepted.
- Selected head files are inspected in full. Findings can predate this pull request; base hashes do not establish a regression diff.
- A policy result covers selected static checks only. Zof does not approve, comment on, or merge the pull request. Changed commits require a new request.
Account and target verification are required for every run. Payment and report access are confirmed by the server.
One-time purchases cover one paid run and do not renew. Paid checks may wait for available service capacity. Prices in USD. You’ll see the total before payment. Terms of use · Privacy policy · Data retention and support.
Before you start
What does the free preview include?
1 selected changed file. The preview shows up to five findings with the scope and limitations of the scan. Zero findings means no issues were detected by those checks, not a guarantee that none exist.
What does a paid run include?
Up to 25 selected changed files in one pull request. A confirmed purchase unlocks the paid allowance and full available findings, plus HTML and PDF exports. Reports remain private to the owning session or account.
Can I check a private target?
Both public and private GitHub repositories require a current selected connection in Billing. Only the saved connection ID is sent with the scan; never include tokens in a repository URL.
