The system component is no longer used under macOS 10.14 (Mojave) and later.
You might want to read this blog post with further explanation.
/System/Library/ScriptingAdditions/TotalFinderSIP.osax
to circumvent the System Integrity Protection (SIP).
You can read some technical details here.
Rarely we might need to upgrade this component. Unfortunately that requires turning SIP off and on again. We maintain this page as a resource with explanation of each upgrade.
v1
TotalFinder 1.9.0 on March 20, 2017
Released in
TotalFinder 1.9.0. This blog post introduced the solution.
Initial version of the component installed with
v2
TotalFinder 1.10.0 on August 21, 2017
Released in
For security reasons
TotalFinderSIP.osax
checks code signature of the code located at/Applications/TotalFinder.app
which it is going to inject intoFinder.app
. It must make sure that the code was produced by us (BinaryAge) and properly signed with a valid developer certificate issued by Apple.
The problem is that in
v1
implementation we were checking specific naming scheme of the developer certificate and Apple decided to change it. As our old certificate expired we were unable to sign new TotalFinder updates in a way which would be recognised by thev1
component as a genuine code coming from us. That is why we had to relax the check inv2
.