If you've ever deployed a macro solution that depends on access to the user's system, then you've probably encountered the support issues related to the module security not being properly set. I've also seen several times on the community where this was a barrier to usability as well - like a blindspot for novice developers and power-users.
This is a simple example of using the API to check module security. The call for the function is included in a sample macro set which will toggle the tabrow visibility. If the security is not set appropriately, a dialog will prompt to instruct steps for correcting the issue and avoiding the infamous script runtime error.
Included in the attachments are the script.txt and example qvw app.
Hope this is helpful!
