bomly-plugin-jvmreach-analyzer
JVM reachability analyzer for Bomly.
It discovers modules in Maven, Gradle, and sbt projects, scans Java, Kotlin,
and Scala sources for import statements, and annotates the vulnerabilities
Bomly already found with package-tier reachability: whether the vulnerable
artifact's packages are actually imported by your code. Results are cached on
disk under <user cache dir>/bomly/analyzers/jvmreach/ (24h TTL).
Safety note: "unreachable" at any tier means the analysis found no path,
not that the vulnerability is safe to ignore. Use reachability to prioritize,
not to dismiss.
Coverage
- Ecosystems: Maven, Scala (Maven, Gradle, sbt builds)
- Languages: Java, Kotlin, Scala
- Tiers: package
- Requires: a source tree, a dependency graph, and vulnerability records from a matcher; Bomly skips the analyzer, with a warning, when a scan cannot supply them. No JVM or build tool is needed.
Access
bomly-plugin.json declares what the analyzer touches, which Bomly shows before you enable it. It is a disclosure, not a sandbox. The import scanner is written in Go and runs in-process: the analyzer needs no JVM or build tool, starts no processes and makes no network calls.
| Access |
Why |
Reads project |
The Java, Kotlin and Scala sources it scans for imports, and the build files (pom.xml, settings.gradle[.kts], build.gradle[.kts], build.sbt) that mark project roots and define modules |
Reads any |
Finding the enclosing multi-module build walks upward from each manifest to the filesystem root, reading pom.xml and settings.gradle in parent directories; a parent build found there becomes the root whose modules are scanned |
Reads and writes cache |
The result cache under <user cache dir>/bomly/analyzers/jvmreach/ |
Environment HOME, XDG_CACHE_HOME, LocalAppData |
Locating the user cache directory (os.UserCacheDir: XDG_CACHE_HOME or HOME on Linux, HOME on macOS, LocalAppData on Windows) |
Embedded in the CLI
The Bomly CLI ships this same analyzer built in — bomly scan --analyze uses
it without installing anything. This repository packages the identical module
as a standalone managed plugin, for lite builds and for hosts that load
analyzers as external plugins.
Install
Download the archive for your platform from the
releases page, then:
bomly plugin install ./bomly-plugin-jvmreach-analyzer_<version>_<os>_<arch>.tar.gz
bomly plugin enable jvmreach
bomly scan --enrich --analyze
Configuration
The analyzer has no configuration keys. Reachability is switched on with the
host's --analyze flag (or the matching config key); caching is on by default
and lives under <user cache dir>/bomly/analyzers/jvmreach/ with a 24-hour TTL.
Local development
go build -o bin/bomly-plugin-jvmreach-analyzer ./cmd/bomly-plugin-jvmreach-analyzer
# Install the dev build into Bomly and scan
bomly plugin install ./bin/bomly-plugin-jvmreach-analyzer --dev
bomly plugin enable jvmreach
bomly scan --enrich --analyze
Run the tests (unit + SDK conformance + a real gRPC handshake probe):
go test ./...
License
Apache-2.0. See LICENSE and NOTICE.