Compliance rules overview

The Compliance module checks whether your repository meets good-standing standards (LICENSE, README, branch protection, CI workflow, security policy…) independent of the architecture rules. It evaluates the repository’s structure and settings rather than code content - most checks look at file presence or your git provider’s settings.

Every scan produces a score (0-100) and per-rule findings. This section documents each rule: what it checks, why it matters, and how to comply.

How findings are produced

1. When you enroll a project for compliance you pick a stack profile (Universal + Integration always apply; Backend/Frontend/Mobile are optional).
2. The scan runs the active rule set against your repository - reading the file tree, README/LICENSE content, and git provider settings.
3. Each rule produces a finding: passed/failed plus a short message. Rules you disable are not scanned and never appear as findings.
4. The score is severity-weighted: Required rules count most, Optional least.

Severity levels

Level	Meaning	Score weight
Required	A baseline standard that should be present.	2.0
Recommended	A strongly advised improvement.	1.0
Optional	Extra credit; nice to have.	0.5

Categories

Documentation · RepositoryHygiene · Security · ContinuousIntegration · Integration

Enabling and disabling rules

From the rules panel you can toggle each rule at the project or workspace level. To keep only the mandatory rules and turn the rest off, just switch off the relevant rules - disabled rules are skipped on the next scan.

Pick a rule from the sidebar for its details.