Findings and policy
Scan depth
Normal and Max scans, and when to use each.
Scan depth sets how thoroughly a scan reviews a change.
| Depth | What it reviews | Default for |
|---|---|---|
| Normal | The change itself. Fast. | Pre-commit scans |
| Max | The change, plus what ingestion learned about the repository: its data storage, routes, entry points, and controls. Slower, and uses more credits. | Pull request scans |
Max catches problems that only show up in context. For example, a new endpoint that skips the permission check every other endpoint in the repository makes.
Who can do this:Team adminsRepository maintainers
To change it, open the repository, go to Settings › Scan policy, and set Scan depth for pre-commit scans and pull request scans separately.
Max needs an ingestion
A Max scan uses the repository summaries from the branch's latest ingestion, or from the default branch if the branch has none. If the repository has never been ingested, a pre-commit Max scan runs at Normal depth and says Used normal effort instead. Run an ingestion to fix it.
Still stuck after reading this page?