Codefend short for "Code Defender" is a Code obfuscator CLI that protects your code regardless of the programming language or framework.\
Visit the official documentation for simple instructions, examples, and advanced settings.
The complete list of examples for different programming languages/frameworks can be viewed here
Please make sure to read the
Philosophy
behind the obfuscation First to understand why Codefend can work with any code written in any language.
npm install -g codefend
codefend -i //required only the first time, generates .codefendrc.json
codefend -o //obfuscates your whole project inside a new directory: 'codefend-output'
npm install -D codefend
In case you want to execute it directly without installing it on your machine:
npx codefend -i //required only the first time, generates .codefendrc.json
npx codefend -o //obfuscates your whole project inside a new directory: 'codefend-output'
Usage: codefend [options]
Defend Your Code By All Means Necessary. 💪 😎
Options:
-i, --init Create the config file (.codefendrc.json)
-o, --obfuscate Obfuscate the project
-c, --check Check the config file for potential warnings/errors
-v, --version Output the version number
-h, --help Display help for command
- Codefend first copy all the files of your project to another directory
by default: /codefend-output
. - Parse every word of every file of your project, searching for patterns in your code.
- Encrypts the detected words (Classes,Functions,Variables...) that matches the pattern.
The only thing Codefend needs from you as a programmer is to follow a specific naming convention for the words that you want to obfuscate
(Classes,Functions,Variables...) and Codefend will do the rest ✨
This basic rule applies to all the languages and the frameworks that you will be programming with while using Codefend to defend your source.
Once your source code is obfuscated you can build the obfuscated version of your code and deploy it
Add prefixes to the words that you want to encrypt.
//as a starting point: prefix the words that should be encrypted with l_
class l_Calculator {
l_sum(l_a, l_b) {
const l_results = l_a + l_b;
return l_results;
}
}
//>>>>>>==== Will Become ======<<<<<<
class Ox0 {
Ox1(Ox2, Ox3) {
const Ox4 = Ox2 + Ox3;
return Ox4;
}
}
// Or for a better organized naming convention:
/**
*
1- class -> starts with c_
2- function -> starts with f_
3- parameter -> starts with p_
4- local variable -> starts with l_
*/
class c_Calculator {
f_sum(p_a, p_b) {
const l_results = p_a + p_b;
return l_results;
}
}
//>>>>>>==== Same results ======<<<<<<
class Ox0 {
Ox1(Ox2, Ox3) {
const Ox4 = Ox2 + Ox3;
return Ox4;
}
}
<!-- Html example, can work also with Angular,React,Vue,Svelte... in the same way -->
<html>
<head>
<style>
.l_red {
color: red;
}
</style>
</head>
<body>
<div class="l_red">l_secret</div>
<div class="l_red">Hello World</div>
</body>
</html>
<!-- Will Become -->
<html>
<head>
<style>
.Ox1 {
color: red;
}
</style>
</head>
<body>
<div class="Ox1">Ox0</div>
<div class="Ox1">Hello World</div>
</body>
</html>
navigate to the root of your project and run the following commands:
codefend -i //required only the first time, generates .codefendrc.json
codefend -o //obfuscates your whole project inside a new directory: 'codefend-output'
/* 1. Navigate to the output folder*/
cd codefend-output
/* 2. Install the dependencies of the new obfuscated project */
npm install
/* 3. Run the obfuscated project */
...
/* 4. Build the obfuscated project */
...
/*⚠️ In case the run or the build fails, most likely its because some reserved words related to your dependencies have been obfuscated.
Solution:
a. Set stats=true in .codefendrc.json (to display a list of the words that are being obfuscated)
b. Detect what are the words that should not be obfuscated from the list displayed
c. Add the words to the ignoredWords array inside .codefendrc.json
d. Repeat 3 and 4 until no Run/Build errors
*/
/* 5.deploy the obfuscated project */
...
Please refer to the configuration section of the docs.
Please refer to the migration guide section of the docs.
## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.
## License
[MIT](./LICENSE.md)