Desktop Application
The desktop application for macOS. Every download is signed with an Apple Developer ID certificate and notarised by Apple. Checking takes about ten seconds. The steps are below.
Not sure which you need? Apple menu › About This Mac. “Chip” means Apple silicon; “Processor” means Intel.
Requires macOS 12 (Monterey) or later. ObraVera is in a closed pilot: the application runs without an account for its offline features, and registering a work requires credentials issued to pilot participants.
On Windows? There is an unsigned pilot kit further down.
Before You Install
The following three commands confirm the file arrived intact, that it carries our signature, and that Apple has seen this exact build. Open Terminal and run them in the folder you downloaded to.
Download SHA256SUMS from the same release, put it beside the disk image, then:
shasum -a 256 -c SHA256SUMS --ignore-missingYou want OK beside your file. Anything else means what you have is not what we published; do not open it.
Replace the filename if you downloaded the Intel build.
codesign --verify --deep --strict --verbose=2 ObraVera-arm64.dmg
codesign --display --verbose=4 ObraVera-arm64.dmg 2>&1 | grep AuthorityThe first prints valid on disk and satisfies its Designated Requirement. The second should name us exactly:
Authority=Developer ID Application: BRADY IAN RIDGWAY (X5937R588J)The name appears on the certificate in capitals. If you see it written any other way, the file is not one of ours. X5937R588J is our Apple Developer Team ID; it is public, and it is in every build we sign.
Notarisation is checked once, at build time; the result travels inside the file.
xcrun stapler validate ObraVera-arm64.dmg
spctl --assess --type open --context context:primary-signature -v ObraVera-arm64.dmgBoth should succeed, and the second should print accepted. That means your Mac can confirm the build without going online — the notarisation ticket is stapled into the file rather than looked up.
If any of the three fails, please do not install the application — and tell us. There is a form for it on the releases repository, which asks for the command you ran and exactly what it printed. If you believe a file was deliberately altered rather than corrupted in transit, report it privately instead of opening a public issue.
Windows
The Windows deliverable is currently a folder of scripts and dependencies rather than an installer. It does not carry a code signature. Windows SmartScreen will warn you about it. An unsigned download is one your computer has no way to attribute to anyone.
We would rather you not click through a warning without knowing why it is there. Check its checksum with the command below, and treat the kit as pilot-only. A signed Windows installer is planned and will replace it. Until then, the macOS builds are the ones with a verifiable chain back to a named developer.
Put SHA256SUMS beside the zip file, open PowerShell in that folder, and run:
$zip = '.\obravera-pilot-kit-windows-amd64.zip'
$sum = Get-Content .\SHA256SUMS | Select-String -SimpleMatch 'windows-amd64.zip'
(Get-FileHash $zip -Algorithm SHA256).Hash -eq ($sum.Line -split '\s+')[0]You want True. False, or an error, means what you have is not what we published — do not extract it. Tell us on the releases repository, or report it privately if you believe the file was deliberately altered.
Every release, with its notes and checksums, is listed on the releases page, and What’s new lists every version’s changes on one page. The buttons above always fetch the current one.