Quality profile

What it means

A quality profile defines which rules a static-analysis tool enables, disables, or configures for a language or project. Profiles make policy explicit and allow teams to tailor checks to framework conventions and risk. A profile should be versioned so a change in findings can be explained.

Example

A team creates a profile for generated API clients that excludes formatting rules but retains security checks. Application code uses a stricter profile with rules for error handling and unreachable branches.

Limitations

A profile can hide problems if exclusions are broad or inherited without review. Rule severity is not the same as actual risk, and different tools may use the same rule name differently. Audit exceptions and keep generated-code boundaries accurate.

How to use the signal

Review exclusions and severity changes as carefully as enabled rules, because a profile can hide risk while appearing standardized.

Weave can associate profile changes with shifts in review findings, rework, and delivery timing. The analyzer remains authoritative for configuration and results; Weave helps assess the operational impact.