Repository navigation
XRAY-167150 - Update Xspecter to 1.9.0 to resolve imported Maven BOMs - #939
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Xspecter 1.8.0 runs Gradle only when allowBuildExecution is set (XRAY-161571). jf audit and Frogbot scan the user's own project, so keep resolving lockfile-less Gradle projects as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
👍 Frogbot scanned this pull request and did not find any new security issues. |
…er 1.9.0 Xspecter 1.9.0 drops the phantom pnpm root built from package.json's main field, and resolves uv.lock into its real tree (3 direct, 4 transitive) instead of listing every package as direct. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
https://jfrog-int.atlassian.net/browse/XRAY-167150
Background
Maven projects that take dependency versions from an imported BOM (
<scope>import</scope>) were scanned withunknownversions byjf audit --static-scaand Frogbot V3, so CVEs in those dependencies were missed.Description
Bump the default Xspecter (xray-scan-lib) version to 1.9.0, which resolves imported BOMs from the local Maven repository. Since 1.8.0, Xspecter runs Gradle only when told to (XRAY-161571), so we now send
allowBuildExecution: true(jf audit and Frogbot scan the user's own project; without it, Gradle projects without a lockfile lose their transitive dependencies).Tests
Local e2e against a real Xray, 1.6.0 vs 1.9.0: a multi-module Maven project with an external parent and an imported BOM now reports
commons-text:1.9and CVE-2022-42889. Gradle, npm, yarn, pip, poetry, go, maven and nuget test projects produce the same SBOM as before.devbranch.🤖 Generated with Claude Code