Protecting my script. Extendscript .jsx/jsxbin to CEP.

[Jibbleton]

So I have written a script with extendscript, only to realise it can be easily decrypted, and shared.  So I would like to protect it and sell it some way without having to rewrite the whole thing in UXP which wasn't quite as well documented when I made the decision to code with the legacy extendscript. Is there anyway I can protect it?

Here are some potential avenues I would like to explore and would be grateful if anyone has any experience or dos/donts etc. 

• Turn it into a CEP plugin like so, basically eval the whole script once fetched. I know it's not overly secure but it feel the script would be better protected than a .jsxbin on its own. I'd b using the legacy interface I made with the the original script. I believe this is possible. It looks like my preferred method...

myCEPPlugin/
├── CSXS/
│   └── manifest.xml
├── js/
│   ├── fetchMyOriginalScriptandEval.js
│   └── CSInterface.js
└── index.html

•  
• Obfuscate .jsx + Encrypt .jsxbin . Basically tie the script with a serial internally so it's only valid with that photoshop. 
  
  
• Refactor all the code to the newest version of UXP. 
  
  Any help much appreciated.

[Stephen Marsh]

There will always be ways to cheat this, so it comes down to how hard you want to make this.

https://www.davidebarranca.com/2016/07/html-panel-tips-22-protecting-your-code/

https://www.davidebarranca.com/2017/02/html-panel-tips-23-javascriptobfuscator-api-gulp-js-plugin/

[Ciccillotto]

If someone is interested in your work and wants to spend time, they will surely be able to decipher it, With uxp I noticed from tests that it is much more complex, So I think you should think about uxp also thinking about the future.