Code signing
ORIX Monitor is distributed outside the Mac App Store, so it is signed with a Developer ID Application identity and the Hardened Runtime, as Apple's notary service requires.
What is signed, and how
| Item | Value |
|---|---|
| Bundle identifier | ai.spboucher.orix.monitor |
| Signing identity | Developer ID Application: Simon-Pierre Boucher (3YM54G49SN) |
| Signing style | Manual, Release configuration only (project.yml) |
| Hardened Runtime | Enabled (ENABLE_HARDENED_RUNTIME = YES) |
| Secure timestamp | OTHER_CODE_SIGN_FLAGS = --timestamp |
| Entitlements | None. No sandbox exception, no JIT, no library-validation exception, no Apple Events |
get-task-allow |
Not present (CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO) |
| Architectures | arm64 only |
| Nested code | None: no helper, no XPC service, no login item bundle, no third-party framework |
The app is not sandboxed. A sandboxed process cannot read the process table, the IORegistry statistics or the interface counters ORIX Monitor exists to show. It compensates by asking for nothing: no entitlement, no privileged helper, no administrator prompt. The only permission it can request is Notification Center, and only when the user presses the button.
Debug builds use automatic signing with an Apple Development identity; they are never distributed.
Procedure
Scripts/build.sh release # xcodegen + xcodebuild Release (signs with the Developer ID identity from the keychain)
Scripts/sign.sh # verification only: identity, Hardened Runtime flag, timestamp, bundle id, entitlements, deep verifyScripts/sign.sh fails if the signature is not a Developer ID Application signature, if the runtime flag or the timestamp
is missing, or if get-task-allow appears. It prints the identity name and team; it never prints key material.
Credentials
The private key lives in the login keychain of the release Mac and never enters the repository. .gitignore excludes
.p12, .p8, .cer, provisioning profiles and keychains, and Scripts/check.sh fails if such a file is tracked.
Requirements checked against Apple's documentation
Read on 2026-11-21 from Notarizing macOS software before distribution (developer.apple.com): Developer ID signature,
Hardened Runtime enabled, secure timestamp, no com.apple.security.get-task-allow set to true, linked against the macOS
10.9 SDK or later, uploads through notarytool (the service no longer accepts altool). The Apple Developer account
pages and App Store Connect were not opened: nothing in this release needs them, and they require the owner's sign-in.