Standards
Repository-wide metric boundaries such as code lines, complexity, file bytes, and longest line.
Enforce standards, document exceptions
Considered evaluates repository metrics against declared standards and records intentional exceptions with their reasons. Keep the policy and the decisions behind it in your repository, and enforce them locally and in CI.
What it records
Violations
Values outside the configured standard. Violations fail checks and deserve attention.
Variances
Reviewed departures from standards, tied to exact files and recorded with a reason.
How evaluation works
- Collect a metric value from its provider.
- Apply the matching standard.
- If the value is within the standard, it passes. Near-boundary values can also be reported as non-failing warnings.
- If the value falls outside the standard, Considered checks for a variance on the exact subject and metric.
- A value inside the variance boundary passes as a visible variance. A missing or out-of-range variance is a violation.