White-Label JavaScript Obfuscation
Budget: $10 – $30 AUD
I run a white-label website service and supply each client with a small JavaScript snippet that injects our widget into their site. The snippet must remain executable exactly as pasted, yet I’d like the underlying logic to be extremely hard to read. I already ran it through several JavaScript obfuscation tools, but the transformed code either broke or was still too transparent, so I need a more robust approach.
Here’s what I’m after:
• A repeatable workflow (CLI script, simple build step, or short Node/Gulp/Webpack task) that takes my original JS, obfuscates it strongly, and outputs a single file I can hand to a client.
• The resulting code has to run in any modern browser with no manual tweaks on the client’s side—just drop-in `<script src="…">`.
• Obfuscation quality should focus on making the source unreadable rather than full-blown encryption, while still preventing quick tampering.
• A brief write-up or screen-share walk-through so I can reproduce the process for every new customer.
You’re free to employ whatever tooling you prefer—Terser, javascript-obfuscator, webpack-obfuscator, custom Babel plugins, or a combination—so long as the final output works reliably with my sample file (attached) and future builds stay one-command simple.
When we’re done I’ll need:
1. The working obfuscated version of the attached script.
2. The automation script / config files.
3. Clear steps (or a short loom/video) showing me how to run it end-to-end.
If you’ve tackled similar white-label or SaaS embedding challenges before, I’d love to see an example. Let’s lock in a straightforward, maintainable solution.
Here’s what I’m after:
• A repeatable workflow (CLI script, simple build step, or short Node/Gulp/Webpack task) that takes my original JS, obfuscates it strongly, and outputs a single file I can hand to a client.
• The resulting code has to run in any modern browser with no manual tweaks on the client’s side—just drop-in `<script src="…">`.
• Obfuscation quality should focus on making the source unreadable rather than full-blown encryption, while still preventing quick tampering.
• A brief write-up or screen-share walk-through so I can reproduce the process for every new customer.
You’re free to employ whatever tooling you prefer—Terser, javascript-obfuscator, webpack-obfuscator, custom Babel plugins, or a combination—so long as the final output works reliably with my sample file (attached) and future builds stay one-command simple.
When we’re done I’ll need:
1. The working obfuscated version of the attached script.
2. The automation script / config files.
3. Clear steps (or a short loom/video) showing me how to run it end-to-end.
If you’ve tackled similar white-label or SaaS embedding challenges before, I’d love to see an example. Let’s lock in a straightforward, maintainable solution.