Frequently Asked Questions

What counts as a Request?

Each time you apply transformations to your project counts as a request, independently of the number of files and protections. Every time this protected version is executed, it does not count as a new service request. The protected version of the code doesn't contact our service. So in summary, you only do Jscrambler service requests when you have a new version of the code to protect.

What happens to my code if I unsubscribe?

Your protected code will continue to work regardless of you staying subscribed or not. You need to keep subscribed only in case you need to protect newer versions of the code. The ones you have protected before will work forever.

Is it possible in a single project to set up different rules for different files?

You can use our Code Annotations to control our transformations through several code blocks

What is self-defending?

Self-defending conceals the logic contained in functions and objects and prevent attempts of code tampering by using anti-tampering and anti-debugging techniques. With these techniques, if someone tries to tamper with the code, the code will break its functionality and if they try to use any JavaScript debugger, it will trigger defenses to prevent code analysis and the code will stop working too.

Should I expect performance hits?

All of Jscrambler's Code transformations are developed to have the least impact possible. The performance hits are manageable and depend a lot on the application you are trying to protect. You can fine-tune your protection on most sensitive parts and apply it more where it is most needed through code annotations.

Do you have command-line tool that I can add to my build process?

You may use an API client if you would like to integrate Jscrambler into your development process and submit requests to our Web service programmatically. Check them out here.

What is potency, cost, and resilience?

Potency represents the power of a transformation to increase your code complexity. Resilience represents the difficulty to revert the transformed code into its original form. Cost represents the impact of a given transformation in execution time and space that it will have in a transformed application.

What are the Application Locks?

The Application Locks are a set of features that allow you to lock your application and your code to a specific environment or criteria. If you develop and sell JavaScript applications for example you’ll want to prevent that someone that didn’t pay or whose license has expired from executing your JavaScript. You can use Domain-Lock can lock your code to a predefined list of domains or OSs. If someone places it anywhere else, it will not execute correctly. You can also use the Date Lock feature to deliver expirable demos to your clients without incurring in the fear of JavaScript code theft or client-loss.