Trivy ignores Maven proxy settings from settings.xml, causing failures in corporate environments
Trivy ignores Maven proxy settings from settings.xml, causing failures in corporate environments: a task in LegoFlow-SWE (Harbor dataset). Trivy’s Java/POM parser currently reads Maven’s settings.xml for repositories, servers, and profiles, but completely ignores the <proxies section. In corporate…
The task
Trivy’s Java/POM parser currently reads Maven’s `settings.xml` for repositories, servers, and profiles, but completely ignores the `<proxies>` section. In corporate environments where outbound HTTP(S) access requires a proxy, this causes resolution failures for parent POMs and metadata because Maven itself does…
Part of Lego-X/LegoFlow-SWE.