Detecting Policy Violations in Build Logs

When the Lineaje GOS Artifactory Proxy is in Enforce Mode, policy violations are surfaced in the build tool's output as part of the HTTP response header. The canonical signal to search for is the string:

Policies violated

This string appears in the response header of any request that is blocked in Enforce Mode. It is consistent across all three supported package managers. To integrate violation detection into your CI pipeline:

Could not transfer artifact org.json:json:jar:20230227 (https://enforce.fortknox.v2.prod.veedna.com/artifactory/gos-all-proxy-maven): status code: 403, reason phrase: Policy violation | Alternate versions: pkg:maven/org.json/json@20231013 | Policies violated: GOS Gold Certification, High vulnerability findings (403) 

The Lineaje platform dashboard provides richer violation reporting, including the specific CVEs, policy rules, and recommended remediation steps for each blocked package.