There are a couple of settings (scopes) that can restrict access to your Drive and to just the Google Doc that the code is running from.
Probably what happens, is that they either don't know about how to do that, or they don't want to do the extra work.
The code editor evaluates the code and automatically decides what permissions needed to be asked for. (Authorized)
But the code editor doesn't have the capability to evaluate all possibilities and choose the most restricted scope.
So, it just automatically uses the most permissive scope.
They should change the code to a more restricted scope. It's a matter of trust.
The scopes can be changed to only allow access to the current Google Doc, and to only files in your Drive that you choose with the Google File Picker.
If that code needs to do a general search of your Drive to find a file or folder, that may be why the Drive scope is using full access.
But if the code doesn't need to search for files that the script did not create, then a more restricted one can be used.
It's more work to add the Google File/Folder picker to the app, and they may not know how to do that.