OpenThunderA workbench for working developers
Make sense of
the code you ship.
Understand your repository. Build with context. Check what changed and see the evidence before your next decision.
Free desktop app for macOS, Windows, and Linux.
Just looking? Try a browser sample →Keep the whole change in view.
From finding your way around a codebase to checking the work you are about to ship.
Find the moving parts.
Explore architecture, dependencies, and critical flows. Give your editor and coding agents context grounded in your repository.
Explore repository context →Build, then challenge the change.
Work with the editor, terminal, and agents. Inspect findings and run relevant checks before deciding what is ready.
Understand Can-I-Ship →Keep the evidence close.
Read what was checked, what failed, and what remains unknown. Follow a result back to the code and the check behind it.
Read the public evidence gallery →Your machine. Or your browser.
Download the desktop app for local work. Try OpenThunder Cloud ↗ to open the hosted workspace. The browser sample is available without installing anything.
Check the release evidence and platform instructions before installing.
Run a review in your project folder.
npx @skillstech/openthunder can-i-ship
Verify this release yourself
Inspect the files behind this release. The release evidence includes: SHA-256 checksums for every artifact, a full CycloneDX SBOM (every resolved dependency with its integrity digest), and SLSA-style provenance recording the source commit and the CI workflow that built them. Don’t take the download on trust; check it:
cd ~/Downloads
curl -fsSLO https://openthunder.dev/releases/OpenThunder-mac-universal.dmg
curl -fsSLO https://openthunder.dev/releases/evidence/SHA256SUMS
shasum -a 256 -c SHA256SUMS --ignore-missing
Re-download the installer so you verify the current build (an older copy in Downloads will not match).
OK means the file on your disk is byte-for-byte the build this evidence describes.
With OpenThunder installed you can verify the whole manifest instead:
openthunder verify-artifacts checksums.json --dir .
Want more proof? See the engine run in public against well-known open-source repos in the Evidence Gallery, or read how Evidence Packs work.
Release history & updates
Read the changes included in each desktop release.
A clear view of what you are using.
Local analysis, cloud workspaces, and optional model calls have different data paths. Read the details for the features you choose.
Take the next step when it helps.
Useful on their own. Connected when you want to learn the code or practise explaining your decisions.