Yes, you can notarize command tools. Doing so ensures independent approval that the code isn’t malicious, and disapproval, letting macOS block code with revoked certificates or notarization.
Notarization
It’s well over 4 years since Apple introduced notarization, but many executables still aren’t properly signed, and require the user to bypass Gatekeeper.
Download some vital free software, mount its disk image, run the Installer package there – but why does Ventura refuse to install it, and what you do?
Checks on app signatures and notarization of notarized apps will be performed each time they’re run. How to deal with problems, and what not to do.
So macOS is being swallowed up into iOS? Haven’t you forgotten how iPadOS is trying to establish itself the middle ground between them?
Is macOS going to be like iOS? Not in Ventura, where notarization is improved with additional security checks. Here are the details.
Overview of supported Macs, Accessory Security, Rapid Security Response, changes coming in notarization, and increasing support for Ukrainian.
There have been changes to the way that macOS 12 checks executable code when asked to run it. Summarised in a diagram.
App signatures remain valid forever, but Installer packages are different, and their certificates can and do expire. What about notarization though?
What are all those files and folders doing inside an app? Which can you safely change to customise an app? Why all the helpers?
The Eclectic Light Company 