Hacking library permissions and make it available to public

I need to send a file with UI-Elements to some person who is not in my team.

So what I do is the following: I collect the elements from my library into a seperate file and save this as a local .fig file.

If you open this fig file with another account, all library components are still components (which is fine) but they are still connected to my team library (which is bad)

you can still get component updates and check out the parent library, even though access of the library is limited to invites only.

So this actually hacks the permission level of the library and is preventing me from sharing the file.

Any ideas on how to solve this for now?

Also if you check people in the “recent contributors” you can see all their files which are available as “anyone with the link”. This might not be intended.