Whet pixel markWhet

Security overview

How Whet is built, signed, checked and updated

For the people who approve software inside an organisation: what Whet sends, how a copy proves it has not been changed, how updates arrive, what is signed and what is not yet, and how to report a problem. Each statement here describes the current release; where something is missing, this page says so.

1. Offline by design

2. Network requests are declared and checked

Every destination the application can contact is declared in one list. A check runs on every build and fails if the shipped code contains a destination that is not on the list. It reads the source, so it cannot see a request a component makes at run time; that is why the privacy policy also says what causes each request. Apart from the version list and the licensed download, which reach getwhet.io only when the user asks, every request goes to a party the user chose: a model provider they attached, a machine they named, or a page they asked Whet to fetch. Addresses on the user's own machine or network are refused as web sources.

An organisation can block all outbound traffic from Whet and lose nothing but those user-initiated requests. With local models only, nothing leaves the machine.

3. Signing and integrity

macOS
The application and the disk image are signed with an Apple Developer ID and notarised by Apple, so Gatekeeper verifies them before first launch.
Windows
The Windows installer and binaries do not yet carry an Authenticode signature, so Windows SmartScreen warns on first run. Verify the installer against the SHA-256 published in the signed release list before installing it.
Linux
The .deb package and the AppImage are not signed with a package signing key. Verify each against the SHA-256 in the signed release list.
The integrity check
Each packaged build carries a manifest of the SHA-256 of every engine file it ships. Before the window runs the engine, it recomputes those hashes, and a copy with a missing or changed file refuses to run and tells the user to reinstall.

4. Updates

5. Installation and data on the machine

6. Third-party components

Every installer carries NOTICES.md, generated from the staged build itself: every engine, every library linked into the window or loaded into the engine, and every package inside the physics interpreter and the engine, with its version, licence and source. The GPL and LGPL source of what ships is in the installer, as the licences page describes. NOTICES.md is the component inventory today; a machine-readable bill of materials in CycloneDX or SPDX format is not yet published.

7. Reporting a security problem

Where
[email protected]. Say which version and platform, what you found, and how to reproduce it. Please do not publish details before a fix is available or ninety days have passed, whichever comes first.
What happens
The report is acknowledged within two working days, assessed, and fixed in a release whose notes credit the reporter if they wish. A fix needed to keep Whet secure is free to every licence holder, whether or not their update window is open.
Good faith research
No legal action will be taken against research done in good faith that respects other people's data and systems and is reported here first. There is no paid bug bounty.

8. What Whet does not have

Stated plainly, because an approval should not rest on an assumption. Whet is made by one person. It has no SOC 2 report and no ISO 27001 certification, and the application has not been tested by an independent penetration tester. Its software is not validated under any quality or regulatory scheme. Questionnaires from a security or procurement team are answered by email at [email protected].

Change log

This version was published on 2026-10-23.