Insertion of paid plugins and the ToS

Hey there!

First off, sorry if this is the wrong category. Let me know if it is and I’ll move it elsewhere. This seems to be the best spot though, since I frequently see posts about the ToS.

Now, I had the idea of creating a plugin that scans your owned plugins’ source code for any malice (especially requiring assets, setfenv, modifying the source of scripts etc). The problem with this is that I’m not sure if doing this on paid plugins is allowed. Since inserting paid plugins only works if you own them, I was wondering if inserting them to be examined was allowed? I would assume that yes, it is allowed since they are available for other users but I don’t know if there was something I had to be careful of since they aren’t free? I’m not saving them anywhere, it’s solely for examining them, then after this all references to the source code would be destroyed.

I would not rely on being able to look inside the contents of paid plugins at all. This behaviour is prone to change in the future.

There is pressure from some paid plugin developers to allow for plugins to be closed-source. To the best of my knowledge, Roblox does not seem to want to do this until their current work with plugin and script permissions is done, at which point no trust in the source code would be needed.

2 Likes

That’s very true. I was also thinking about the fact that paid plugins are only open to a certain number of individuals, and those individuals are trusted so scanning them would be redundant.