Security fix: finding from an SBOM

What it means

Returned by POST /orgs/{org}/code-security/deps/findings/{id}/autofix (Security fixes). No pull request was requested.

Since 2026-10-14 the same refusal is answered with the type security-fix-sbom-finding from POST /orgs/{org}/dependency-updates/security-fixes/requests. The paths above are deprecated and keep answering autofix-sbom-finding until 2027-10-15. Branch on either type.

Example detail message returned with this error:

• This finding comes from an uploaded SBOM, not from a manifest in the repository, so there is no file for a security fix to change.

The response also carries "reason": "sbom_finding".

What to do

The finding was raised on an SBOM you uploaded (its manifest is sbom:<name>), so no file in the repository declares the dependency. Fix it where the SBOM comes from.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/autofix-sbom-finding",
  "title": "Unprocessable Entity",
  "status": 422,
  "detail": "...",
  "reason": "sbom_finding"
}

Branch on type, not on title or detail - those are human-readable and may be reworded.