What is knowingly left undone in the desktop application. Nothing here blocks the app from working; each entry says what breaks, and when. The engine keeps its own list in silentsilo/core: storage backends, key rotation and the extraction tool.
The Windows installer is code-signed, so a download can be checked against the publisher. It cannot yet be checked against the source: two people building this commit do not get the same bytes, so the only thing tying the binary to the code published here is trust in whoever built it. The cryptography specification in core names a tampered binary as the path nothing inside the program can defend against, and a reproducible build is the half of the answer still missing.
Windows and, from 1.4, Linux ship. The release workflow builds a macOS bundle, and signs and notarises it once the Developer ID secrets are set; no macOS build has been tested on a Mac yet, so none is released. The crates underneath build and are tested on macOS in silentsilo/core.
Surveyed on 21 August 2026 across the 534 components that ship: MIT,
Apache-2.0, BSD, ISC, Zlib, Unicode-3.0, MPL-2.0 and a few public-domain
dedications. All permissive, all compatible with AGPL-3.0, and none
undeclared. Their notices are generated by npm run notices and installed
beside the application as THIRD-PARTY-NOTICES.txt.
That is a survey of declared licences, not a legal audit. Nobody has checked whether a component's declared licence matches what is actually in it.