Distribution
Artifacts (version 1.0.0, build 1)
| File | Bytes | SHA-256 |
|---|---|---|
ORIX-Monitor-1.0.0.dmg |
3,455,660 | 76ae76570e2c7654cdf377922bc85967d04eb20eedeaabd7675791f5b84e3be2 |
ORIX-Monitor-1.0.0.zip |
2,515,813 | 3b91a67ff51dd880bc1250491b1abc6591a95349717318139571023bcf1ad752 |
SHA256SUMS.txt |
— | the two lines above, in shasum -a 256 format |
| Property | Value |
|---|---|
| Minimum macOS | 15.0 |
| Architecture | arm64 |
| Signing | Developer ID Application, Hardened Runtime, secure timestamp, no entitlements (signing) |
| Notarization | Accepted for the app and the disk image, both stapled (notarization) |
| Installed size | about 6.7 MB |
They are in dist/ on the release Mac. dist/ is ignored by git: binaries are not committed.
The disk image
Built by Scripts/package.sh dmg with create-dmg: a 660 × 440 pt window on the ORIX canvas, the app icon on the left, an
alias to /Applications on the right, an arrow between them and the line "Drag ORIX Monitor to the Applications folder".
The background is drawn by Scripts/tools/dmg-background.swift. The image is UDZO-compressed, signed with the same
Developer ID identity, notarized and stapled. hdiutil verify reports its checksum valid.
The ZIP
ditto -c -k --keepParent of the stapled app, for people who prefer not to mount an image.
Where it is published
Published on 2026-11-21, at the owner's request.
The repository was private (gitsrv:srv/git-private/orix-monitor.git, SSH only) until then, as the brief required; the
forge has no private mode, so publishing the release meant publishing the source.
What was done
spbgit create orix-monitor -d "…" --topics "macos,swift,swiftui,…"
git remote set-url origin gitsrv:srv/git/orix-monitor.git && git push origin main --tags
spbgit release upload orix-monitor v1.0.0 dist/ORIX-Monitor-1.0.0.dmg dist/ORIX-Monitor-1.0.0.zip dist/SHA256SUMS.txt dist/RELEASE-NOTES.mdVerification after upload
The three files were downloaded from the public URLs into an empty directory: HTTP 200, 3,455,660 / 2,515,813 / 178 bytes;
shasum -a 256 -c SHA256SUMS.txt reported both files OK; xcrun stapler validate succeeded on the downloaded disk image
and spctl answered accepted, source=Notarized Developer ID. The repository page and the releases page answer HTTP 200.
Updates
No automatic update mechanism ships in 1.0.0. Sparkle was considered: it is the mature choice for Developer ID apps, with EdDSA-signed updates over HTTPS and user control. It was left out because an update framework without a verified, signed release feed is worse than none, and no appcast feed has been set up. The app performs no update check and makes no network request of its own.