Releases
v4.5
One command to install, update and run a host, updates that keep your settings, a doctor that says what is wrong, and a release an installation can name and verify.
v4.5 is about the installation itself. One command installs, updates and runs a host; updating is a single step that keeps your settings; and an installation can say which release it runs and prove the files it runs are the ones that were published.
| Area | What changed |
|---|---|
| One command | ./scansuite install, update, start, stop, restart, status, logs, doctor, version, reset, dojo, offline and uninstall. The older names remain as shortcuts, so existing scripts keep working. |
| Updating in one step | update saves the settings, fetches the release, pulls the images for your licence, refreshes the boot service and recreates only the services that changed. |
| An upgrade that cannot conflict | The release a host runs is a setting in .env rather than a value edited into docker-compose.yml, so the installation files update cleanly every time. |
| doctor | One pass over Docker, the ports, disk space, the clock, the licence, the certificate, the settings and the services — every check reported, not just the first failure. |
| Starting means healthy | start and restart wait until each service reports healthy and name the one that did not, instead of pausing and reading the logs for a hopeful line. |
| Secrets per installation | Database and queue passwords are generated on the first install and the timezone is taken from the host, so no installation ships with a password anyone else knows. |
| A release with a name | Every installation carries a RELEASE file and checksums for everything it runs; version prints the release, what it was built from, the licence and the images actually running. |
| Scanners as a list | The scanner images an installation pulls are a file in the release, so the set can change without a new installer. |
| Offline installs | offline save and offline load move a verified set of images to a host with no registry access. |
| A current certificate | The certificate shipped with an installation is valid for ten years. It is still self-signed and still meant to be replaced. |
| Infrastructure assets by product | Infrastructure assets are grouped by product, the management screens follow, and the infrastructure agent keeps its scanner evidence and records how each run ended. |
| Steadier integrations | ServiceNow exports carry the product name as the hostname, pending Nessus scans and failed report exports are handled rather than retried blindly, and a repository submodule that cannot be fetched warns instead of failing the scan. |
Last reviewed 2026-09-20