The way it works is that you can export your cooked project from the menu.
Once you've picked your path, MAT will ask you whether you want to just cook, or cook and secure:
Now that it's cooked, the user can copy the IMP to his library in Documents/
Once loaded it will show up in the library and it can be used like any other node:
However, trying to open the node by double-clicking and MAT refuses to open it:
When trying to open the package directly using the open package option, it also refuses it:
¶ Cooking projects that reference a securely cooked library package project
If you cook a project that uses a node or project from a cooked package, MAT will not include that project in the project that is now being cooked. This is done to avoid leaking of data but causes a hidden dependency as a project that has a dependency on your cooked library package may not load if your cooked package that contains this dependency is not available in the user library.
¶ Are there other ways to crack open a securely cooked library package?
I'm not aware of other ways to open/load/inspect/extract data from a package so I believe this is secure and implements the requirements.