Replies: 1 comment 4 replies
-
Since we use the default client, the proxy environment variables should be respected. @DmitriyLewen Any ideas? trivy/pkg/dependency/parser/java/pom/parse.go Lines 744 to 745 in 49d5270 BTW, we should improve the debug message to show the detailed error or the status code. trivy/pkg/dependency/parser/java/pom/parse.go Line 747 in 49d5270 |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Question
Description
Hey #trivy.
We have been using Trivy to scan different open-source packages, including NPM and Maven. However, we are encountering an issue when scanning a Maven package. We are using another service to download the required package from the Central Maven Repository, and the data is being shared between the services using a volume.
We treat the packages as a 'filesystem' and scan the target directory where the pom.xml file is stored and the dependency directory, which includes the *.jar files.
Desired Behavior
We expected the scan to succeed and fetch the URL.
Actual Behavior
We encountered an issue while running the following command:
trivy fs --skip-db-update --skip-java-db-update --debug --scanners vuln,license --license-full --severity UNKNOWN,HIGH,CRITICAL --format json -o /app/shared_data/trivy-report.json /app/shared_data /target
Note:
HTTPS_PROXY="http://domain:port"
HTTP_PROXY="http://domain:port"
Has anyone encountered the same issue?
Target
Filesystem
Scanner
Vulnerability
Output Format
JSON
Mode
Standalone
Operating System
Ubuntu
Version
Beta Was this translation helpful? Give feedback.
All reactions