# Basic Code Obfuscation ## :scales:Obfuscation Metrics 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. ### :fast\_forward:Performance 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. ### :brain:Resilience 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. ### :closed\_lock\_with\_key:Potency **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](https://en.wikipedia.org/wiki/Cyclomatic_complexity) and [Halstead complexity](https://en.wikipedia.org/wiki/Halstead_complexity_measures). 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. ### --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cyphor.net/.net-code-obfuscation/code-obfuscation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.