Find out why a rule does not apply
A rule that does not fit a repository reads n/a there: a Go linter rule on a repository with no Go code, a rollback rule on one that deploys nothing. An n/a rule neither passes nor fails, so it never shows as a gap. When a rule you expected to see is missing from a project's gaps, check whether it is n/a and why.
Who can do this: anyone who can see Compliance. Correcting a fact needs the permission to edit compliance on the project. Compliance is part of some plans only.
-
In the sidebar, select Compliance. On the Repos tab, select the project's name to open its page.
-
Select the Rules tab. The list shows every rule of the pack by pillar.
-
Open the dropdown above the list, which reads All, and select n/a. Only the rules that do not apply to this repository stay, grouped by why.

-
Read each group's heading. It starts with n/a: and gives the reason once for every rule under it, with how many rules it holds, such as "n/a: This repo has no Terraform. (1)". A heading that reads n/a for this stack gives no more detail.
-
To see what the rule needs, select its name. The rule's page opens; Applies when lists the facts a repository needs for the rule to apply.
-
To see what the scan looked at on this repository, go back and select Evidence on the rule's row.
-
If the reason is wrong, for example the repository does have Go code, go back to the project's Overview tab and correct the fact under Facts (N), as in Correct a fact a scan detected. Then select Rescan at the top of the page. When the scan finishes, the rule is scored and leaves the n/a list.
When no rule is n/a on the repository, the list says "No rule is n/a here."
A rule limited to other repositories reads Out of scope instead and is not in the n/a list. To change which repositories a rule covers, see Limit a rule to some repositories.
Related
- How compliance works: results, facts and how a scan decides where a rule applies.
- See where a rule fails: every repository failing one rule.
- Repository compliance: every field on the repo page's Rules tab.