All six exist: macOS on Apple Silicon and Intel, Windows on x64 and ARM64, Linux on x64 and ARM64. Each one carries its real size and its real SHA-256 below, because the geometry engine is compiled per platform and the only way to know you have the right binary is to check it.
Version 1.0.0 · no account, no installer telemetry.
All six platforms
01
Your own platform is marked below. A build with no file yet is marked Not built yet rather than left off the table or linked to something that 404s.
Before you open it
02
It will, and that is on us. The build is signed with a real Developer ID — MINIMALI LLC — but it is not notarised yet, and notarisation is the step that dialog is complaining about. Right-click the app in Applications, choose Open, then Open again on the dialog. macOS remembers, and you never see it again.
Do not run xattr -d com.apple.quarantine on it. You will find that advice everywhere and it is the wrong habit: it strips the quarantine flag off whatever you point it at, which is exactly the check you want working the next time something less honest asks you to run it. Right-click → Open does the same job for this one app and leaves the rest of the machine alone. This answer comes off the page the day notarisation lands.
It will, and that is on us too. The Windows installer is not code-signed — there is no certificate yet — so SmartScreen stops an app it has never seen before. Click More info, then Run anyway. That is the whole bypass, and unlike the macOS one it still works normally.
Do not turn SmartScreen off. It is doing its job; it simply has nothing on file about a build this new. This answer comes off the page the day the installer is signed.
Both Windows builds are compiled on Windows — the geometry engine is a C++ addon and a compiled binary only runs on the machine type it was built for, so there is no cross-built shortcut here. The ARM build is a genuine ARM64 binary, not the x64 one under emulation.
Download it, make it executable, run it. Nothing installs and nothing needs root:
chmod +x RivetPCB-1.0.0-linux-x64.AppImage && ./RivetPCB-1.0.0-linux-x64.AppImage
There is no publisher check to fail on Linux and no warning to click through — which is also why the SHA-256 above is the only thing telling you the file is the one we built. Check it.
No. It is its own editor with its own engine, compatible with KiCad: it ships the KiCad symbol and footprint libraries, reads them, and writes symbols and footprints back out in the same format. Your existing parts open. Your work leaves.