A lightweight and extendable Java 8+ CLI tool for auditing and diagnosing Windows developer environments.
Originally created after a real recovery incident, this tool helps validate that common development tools, SDKs, and environment variables are correctly installed and discoverable. Easily extendable to fit your use case.
Windows only ; it relies on
cmd,where,wmic, and Windows install conventions.
- Windows
- Java 8+
- Maven (for building)
Detects common development software installations and reports whether they're present.
check-installation #uses default software list
check-installation --export #export report as .txt file
check-installation --config software.json #load json entries from file[
{
"name": "node",
"exe": "node",
"version": "node --version"
},
{
"name": "Visual Studio"
}
]Software | Path | Version | Found
---------------------------------------------------------------------------
node | C:\Program Files\nodejs\node.exe | v20.11.0 | [x]
npm | C:\Program Files\nodejs\npm.cmd | 10.2.3 | [x]
python | - | - | [ ]
java | C:\Program Files\Java\jdk...\bin | 21.0.1 | [x]
vscode | C:\Users\...\Code.exe | 1.86.2 | [x]
Visual Studio | C:\Program Files\Microsoft VS\ | 2022 | [x]
.NET SDK | - | 8.0.100 | [x]
Recursively find and delete node_modules folders given a root path.
clean-node-modules <path> #asks for confirmation y/N before deleting
clean-node-modules <path> --silent #no confirmation
clean-node-modules <path> --dry-run #lists what would be deleted but doesn't deleteDetects Node, Java, .NET projects recursively.
scan-projects <path>Node: 12
Java: 5
.NET: 3
Python: 2
Checks common environment variables that often break builds.
env-check <path>JAVA_HOME: SET
NODE_ENV: NOT SET
PATH: SET
HTTP_PROXY: NOT SET
HTTPS_PROXY: NOT SET
mvn package- PicoCLI.
