Summary
The build, not just the source.
Most code servers stop at reading files. This one runs the Gradle build and its tests, and can bump a dependency and then show what the new JAR changed — which is the loop an upgrade actually is.
What it is
A build-system client for JVM-centred projects. It detects which build system a directory uses — Gradle, Maven, NPM or Yarn, Cargo, Python, Makefile or CMake — reads and updates dependency versions, and runs Gradle builds and test tasks directly.
What you get
- The build system in a directory identified, with the paths to its build files
- Top-level dependencies listed with their versions, and the latest available version fetched from the repository
- A dependency version written back into the build file itself
- Gradle builds run with checks optional, and Gradle test tasks run as their own step
- Class usage traced across the codebase, for when the question is what a change would break
- Two JAR files compared, so what a version bump actually changed is visible
- File and resource metadata, whole-file source replacement, and the latest source pulled down
Requirements
A Java runtime — the server builds with Gradle into a JAR, with an experimental native image alongside it. Gradle itself must be usable for the build and test tools; the rest only read your project files.
Setup effort
One command — scout