Basic Code Obfuscation
Obfuscation is the main feature that distinguish our service.
Our online panel and documentation show up to three different metrics, they are important as they help to measure the obfuscation quality and repercussion the applied techniques will have in your protected files.
The performance metric reassembles the overall cost that an obfuscation technique has on your file, this includes but is not limited to: execution time, compilation time and, size of the new code.
Resilience measures how persistent an obfuscation technique is. In most scenarios obfuscation transformations can be reversed, resilience measures how strong a feature is against attacks that aim to automate the removal of the protection (commonly known as deobfuscators).
Some features, such as Symbol renaming or Code Inlining/Outlining have the highest level of resilience, the reason for this is due to the fact they can't be reverted back to their original shape.
Potency measures the complexity that your code has after obfuscation, this metric is targeting humans as attack vectors. In order to calculate this metric, we took advantage of some existing algorithms that measure how complicated code is to the human eye. Cyclomatic complexity and Halstead complexity.
There are exceptions to this measure, for example, some of our features might encrypt your code or parts of it, this makes the potency the highest level possible as the code is not even readable for the human eye.
Last updated