Every build, with its hash, for independent checking.
Every version has two builds: light, the default with no capture driver, and field, for a customer who wants live capture and accepts the driver install. The size and SHA-256 of each file are on this page; check them before you run anything.
Updated: 17 November 2026
Current
GridSight 0.10.0
A second sample network with two GOOSE publishers and a real SV publisher, a guide rendered from the build so it can never drift, and a reviewer guide inside both packages.
light — the default build
light · 0.10.0
No capture driver. Follows a capture file another tool is still writing, or analyses a finished one. For every buyer.
The same code, plus a capture driver and a consent screen. Before the first live capture it asks to install the driver and confirms the site’s permission; declining leaves every other feature working. Never the default download.
The review package: one command turns a substation folder into the seven files a customer receives, with a reproducible manifest. The report prints to A4 from the browser.
light — the default build
light · 0.8.0
No capture driver. Follows a capture file another tool is still writing, or analyses a finished one. For every buyer.
The same code, plus a capture driver and a consent screen. Before the first live capture it asks to install the driver and confirms the site’s permission; declining leaves every other feature working. Never the default download.
The same code, plus a capture driver and a consent screen. Before the first live capture it asks to install the driver and confirms the site’s permission; declining leaves every other feature working. Never the default download.
Both builds are unsigned and a code-signing certificate is pending. Windows SmartScreen will warn on first run; this is not a signed release.
The field build carries a capture driver the customer consents to install. In this release the bundled driver is a labelled test double: it installs nothing and captures nothing.
SHA-256
Check before you run it
In PowerShell, in the folder you saved the file, run the command below and compare the output with the value on this page. If they differ, do not run the file.