See where a rule fails
Before you fix a rule everywhere, waive it or make it stricter, check how far it reaches: which repositories fail it, since when, what the check found in each, and who has waived it. A rule's page lists all of that in one place.
Who can do this: anyone who can view compliance. You see only the repositories of projects you can see. Compliance is part of some plans only; while your organization's plan leaves it out, Compliance is not in the sidebar. You need results first: run a scan if you have none.
-
In the sidebar, select Compliance. The page opens on its Repos tab.
-
Find a row whose Next gap names the rule. Hover the name to read why it matters, then select it to open the rule's page. To reach a rule no row names, select Settings in the sidebar, then Compliance Packs under Customize, open the pack marked Active, select its Rules tab and select the rule.
-
Read the header: the rule's name and, under it, its pillar and level, such as L2. Further down, Intent and Why it matters say what the rule asks for, Applies when which repositories it applies to, and How it is checked what the scan looks at.
-
Read Failing repos: the count, then one line per repository that fails the rule, with since and when it started failing. If it reads Passes on every scanned repo you can see., nothing is failing.

-
Select Evidence beside a repository to see what the check found there: What was checked, the Commit and when it was Scanned, and What was found. Select the repository's name instead to open its whole compliance page.
-
Check Not scanned, shown only when it has rows: repositories whose last scan of this rule did not finish. They are not counted as failing, so rescan them before you rely on the count.
-
Check Active waivers, shown only when the rule has some: each waived repository with how long its waiver lasts, its Owner:, the reason and its Control:. A waived repository is not a gap until the waiver ends.
-
Where your organization has the Architectural Guard and the rule stopped at least one agent change in the last 30 days, Guard blocks shows how many, such as 3 in 7 days · 12 in 30 days. Select it to open the list of those blocks.
A change rule, whose header reads Change rule, has no Failing repos: it judges agents' changes as they are made, not repositories, so its Guard blocks are what to read. That line shows only when the rule blocked something in the last 30 days: without it, the rule stopped nothing in that time.
Related
- Fix a rule across many repositories — file one fix per failing repository with a campaign.
- Waive a compliance gap — accept the rule failing on one repository for a set time.
- Change how strictly a rule is enforced — raise, lower or turn off the rule once you know where it fails.
- Review what the guard blocked — the changes a rule stopped, one by one.
- Repository compliance — every field on a rule's page.