js-confuser 2.0.0-alpha.5 → 2.0.1

package/CODE_OF_CONDUCT.md

@@ -1,132 +1,132 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-michaelxfr@gmail.com.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
-
-Community Impact Guidelines were inspired by 
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
-at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+michaelxfr@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by 
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -1,53 +1,53 @@
-# Contributing to JS Confuser
-
-## Setup
-
-1 Clone your fork of the repository
-```
-$ git clone https://github.com/<USERNAME>/js-confuser.git
-```
-
-2 Install npm dependencies
-```
-$ npm install
-```
-
-3 Create a `dev.ts` file in the root directory, ex:
-```js
-import JsConfuser from "./src/index";
-
-JsConfuser.obfuscate(`<source code>`, { /* options */ }).then(obfuscated=>{
-
-  console.log(obfuscated)
-  eval(obfuscated);
-})
-```
-
-The `dev.ts` file is only used for fiddling with the library. It uses `@babel/register` to transpile code on the fly.
-
-4 Run the dev file
-```js
-$ npm run dev
-```
-
-5 Run Tests before committing
-```
-$ npm run test
-```
-
-## Code Style
-
-Indent: 2 spaces
-Recommended Extension: [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode)
-
-## Guidelines
-
-- Please try to [combine multiple commits before pushing](http://stackoverflow.com/questions/6934752/combining-multiple-commits-before-pushing-in-git)
-
-- Please use `TDD` when fixing bugs. This means that you should write a unit test that fails because it reproduces the issue, 
-then fix the issue and finally run the test to ensure that the issue has been resolved. This helps us prevent fixed bugs from 
-happening again in the future
-
-- Please keep the test coverage at 95+%. Write additional unit tests if necessary
-
+# Contributing to JS Confuser
+
+## Setup
+
+1 Clone your fork of the repository
+```
+$ git clone https://github.com/<USERNAME>/js-confuser.git
+```
+
+2 Install npm dependencies
+```
+$ npm install
+```
+
+3 Create a `dev.ts` file in the root directory, ex:
+```js
+import JsConfuser from "./src/index";
+
+JsConfuser.obfuscate(`<source code>`, { /* options */ }).then(obfuscated=>{
+
+  console.log(obfuscated)
+  eval(obfuscated);
+})
+```
+
+The `dev.ts` file is only used for fiddling with the library. It uses `@babel/register` to transpile code on the fly.
+
+4 Run the dev file
+```js
+$ npm run dev
+```
+
+5 Run Tests before committing
+```
+$ npm run test
+```
+
+## Code Style
+
+Indent: 2 spaces
+Recommended Extension: [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode)
+
+## Guidelines
+
+- Please try to [combine multiple commits before pushing](http://stackoverflow.com/questions/6934752/combining-multiple-commits-before-pushing-in-git)
+
+- Please use `TDD` when fixing bugs. This means that you should write a unit test that fails because it reproduces the issue, 
+then fix the issue and finally run the test to ensure that the issue has been resolved. This helps us prevent fixed bugs from 
+happening again in the future
+
+- Please keep the test coverage at 95+%. Write additional unit tests if necessary
+
 - Please create an issue before sending a PR if it is going to change the public interface of Js Confuser or includes significant architecture changes

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2021 MichaelXF
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2021 MichaelXF
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/Migration.md

@@ -1,72 +1,73 @@
-## Migration guide to JS-Confuser 2.0
-
-JS-Confuser 2.0 is complete rewrite of the original JS-Confuser created in 2020!
-
-## API Interface changed
-
-### JSConfuser.obfuscate() returns an object now
-
-The method `JSConfuser.obfuscate()` resolves to a object now instead of a string. This result object contains a property `code` which is the obfuscated code.
-
-```diff
-const sourceCode = `console.log("Hello World")`;
-const options = {
-  target: "node",
-  preset: "high"
-};
-
-JSConfuser.obfuscate(sourceCode, options).then(result=>{
-  // 'result' is now an object
-- console.log(result);
-+ console.log(result.code);
-});
-```
-
-### Removed Anti Debug Lock / Browser Lock / OS Lock
-
-These features have been removed but you can still add these locks using the `lock.customLocks` option.
-
-```js
-{
-  target: "node",
-  
-  // ... Your obfuscator settings ...
-
-  lock: {
-    customLocks: [
-      {
-        code: `
-        // This code will be sprinkled throughout your source code
-        // (Will also be obfuscated)
-
-        if( window.navigator.userAgent.includes('Chrome') ){
-          {countermeasures}
-        }
-
-        // The {countermeasures} template variable is required.
-        // Must be placed in a Block or Switch Case body
-        `,
-        percentagePerBlock: 0.1, // = 10%
-        maxCount: 100, // Default = 100 - You probably don't want an excessive amount placed
-        minCount: 1 // Default = 1 - Ensures this custom lock is placed
-      }
-    ]
-  }
-}
-```
-
-### Stack renamed to Variable Masking
-
-The option `stack` has been renamed to `variableMasking`
-
-[Similar to JScrambler's Variable Masking](https://docs.jscrambler.com/code-integrity/documentation/transformations/variable-masking)
-
-```diff
-const options = {
-  target: "node",
-  preset: "high"
-
-- stack: true,
-+ variableMasking: true
-};
+## Migration guide to JS-Confuser 2.0
+
+JS-Confuser 2.0 is complete rewrite of the original JS-Confuser created in 2020!
+
+## API Interface changed
+
+### JSConfuser.obfuscate() returns an object now
+
+The method `JSConfuser.obfuscate()` resolves to a object now instead of a string. This result object contains a property `code` which is the obfuscated code.
+
+```diff
+const JSConfuser = require("js-confuser");
+const sourceCode = `console.log("Hello World")`;
+const options = {
+  target: "node",
+  preset: "high"
+};
+
+JSConfuser.obfuscate(sourceCode, options).then(result=>{
+  // 'result' is now an object
+- console.log(result);
++ console.log(result.code);
+});
+```
+
+### Removed Anti Debug Lock / Browser Lock / OS Lock
+
+These features have been removed but you can still add these locks using the `lock.customLocks` option.
+
+```js
+{
+  target: "node",
+  
+  // ... Your obfuscator settings ...
+
+  lock: {
+    customLocks: [
+      {
+        code: `
+        // This code will be sprinkled throughout your source code
+        // (Will also be obfuscated)
+
+        if( window.navigator.userAgent.includes('Chrome') ){
+          {countermeasures}
+        }
+
+        // The {countermeasures} template variable is required.
+        // Must be placed in a Block or Switch Case body
+        `,
+        percentagePerBlock: 0.1, // = 10%
+        maxCount: 25, // Default = 25 - You probably don't want an excessive amount placed
+        minCount: 1 // Default = 1 - Ensures this custom lock is placed
+      }
+    ]
+  }
+}
+```
+
+### Stack renamed to Variable Masking
+
+The option `stack` has been renamed to `variableMasking`
+
+[Similar to JScrambler's Variable Masking](https://docs.jscrambler.com/code-integrity/documentation/transformations/variable-masking)
+
+```diff
+const options = {
+  target: "node",
+  preset: "high"
+
+- stack: true,
++ variableMasking: true
+};
 ```