Function code_scanning_incompatibility 

pub fn code_scanning_incompatibility(
    provider: Option<Provider>,
    driver: Option<&str>,
    forge: Option<&str>,
) -> Option<String>

Why the named code scanning provider cannot run at this (technology, forge), or None where it can or none is named.

One owner for the question, because two callers ask it and they must not disagree. The reason is informational: it becomes the catalog’s Unavailable status, and nothing refuses on it. An optional capability this release cannot build at the target’s dimensions is reported and omitted, which is what project-profile:an-operation-refuses-only-what-it-requires states.

A receipt asks the same question and gets the same answer, because Params::from_record cannot fail and a hand-edited or foreign receipt reaches rk status through it: without this, a receipt naming a provider whose pair ships nothing would project nothing, name nothing, and read as clean. It is a report about the pair, not a record defect, so a landing this binary wrote still answers its own check.