Repository navigation
feat(manifest): add socket.json reachability settings for the build tools - #1728
Conversation
2c50fc1 to
4019231
Compare
4019231 to
4e3d59e
Compare
PR SummaryMedium Risk Overview Settings cascade field-by-field (with Only reachability scans ( Reviewed by Cursor Bugbot for commit 4e3d59e. Configure here. |
4e3d59e to
ca1a152
Compare
687be27 to
db94aec
Compare
db94aec to
e24fc2b
Compare
e24fc2b to
700bf18
Compare
A build tool's socket.json section takes a `reachability` object, which reachability scans send to Coana with each build root's request: - `build`: "compile" builds the project before the analysis, "none" or unset analyses it unbuilt; - `javaHome`, Maven, Gradle and sbt: the JDK the analysis takes the program to run on, as written; - `runtimeVersion`, .NET: the runtime a framework-dependent build's analysis starts on, as major.minor or major.minor.patch[-prerelease]. Each field cascades on its own, a build's own `builds` entry last, and null clears an inherited one. Only a reachability scan reads them, for the build tools it runs, so an invalid value never stops another command. It checks them before any build runs and fails naming the socket.json and setting, including a field the build tool does not take.
700bf18 to
15420b3
Compare
Heads up, reviewer
Reachability analysis can use different settings than sbom generation, e.g. analyse against a different java/dotnet runtime.
Additionally, customers may want to build their projects for reachability analysis, but not when just generating sboms.
This PR adds
reachabilitysettings to socket.json to help configure such properties.LLM Description written by Claude Code:claude-opus-5-5
A build tool's socket.json section, and a build's own
buildsentry, take areachabilityobject that reachability scans send to Coana with each build root's request: whether to compile the project before the analysis, and the JDK or .NET runtime the analysis assumes.Merges with the stack; the release gates and the expected e2e failures are in #1725.
Settings
build:"compile"builds the project first, and a failed build fails the scan;"none"or unset analyses it unbuilt.javaHome(Maven, Gradle, sbt): the JDK the analysis takes the program to run on, passed as written; unset, the build's own JDK.runtimeVersion(.NET): the runtime a framework-dependent build's analysis starts on;major.minortakes its latest installed patch,major.minor.patch[-prerelease]exactly that runtime.Cascade and validation
buildsentry last;nullclears an inherited value.Stack
Changelog
In
CHANGELOG.mdunder[Unreleased]:Added
socket.json:reachability.buildcompiles the project before the analysis,reachability.javaHome(Maven, Gradle, sbt) sets the JDK the analysis assumes, andreachability.runtimeVersion(.NET) sets the runtime it starts on.🤖 Generated with Claude Code