Produce a compliance report for auditors¶
When you need to demonstrate conformance to a standard, generate a Compliance Report. It lists every check in the standard and its status.
What it shows¶
For each check in the configuration, the report's Compliance column shows:
| Status | Meaning |
|---|---|
| Compliant | No violations for this check. |
| Not Compliant | One or more violations remain. |
| Not Supported | This rule isn't automatically checkable by Understand (needs manual review). |
The Not Supported rows are the key to an honest audit: they're the standard's rules that require manual review, matching the automated-coverage percentages in which standard. Pair the report with in-code deviations so accepted violations are documented with rationale.
Generate it¶
Run an inspection against the standard's configuration, then open the Compliance Reports section
on the CodeCheck dashboard (it's surfaced separately from the other inspection reports) — see the
Codecheck Report reference page. You can also
produce reports headlessly with und codecheck -reports.
To track conformance as a number over time, the violation-density metrics (by code lines / by lines) complement the per-rule report; for the HIS metric limits specifically, see HIS metrics.
Safety qualification
For DO-178C / functional-safety qualification, see the certification/qualification materials (contact SciTools) — this page covers the standard conformance report, not the full qualification kit.