Renamed config files to disable instrumentation, updated README file

cristianstaicu · Sep 2, 2022 · e44dd95 · e44dd95
1 parent 959c5a6
commit e44dd95
Show file tree

Hide file tree

Showing 9 changed files with 4 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -153,6 +153,6 @@ If any of the test fail failed to run from the roor folder, please run it in the
 
 ## Important Scripts
 
-One of the important features of Secbench.js is extendability. It is possible to add new analysis to the existing code to run dynamic analysis. For example, our test cases can be extended using bable analysis. To get the sink location for the exploits, we extend our analysis using `jest.config.json`, where we added our custom analysis code. Each exploit category folder includes `jest.config.json` file which can be used to add new analysis code.
+One of the important features of Secbench.js is extendability. It is possible to add new analysis to the existing code to run dynamic analysis. For example, our test cases can be extended using bable analysis. To get the sink location for the exploits, we extend our analysis using `jest.config.json`, where we added our custom analysis code. Each exploit category folder includes `jest-analysis.config.json` file which can be used to add new analysis code. In order to enable the instrumentation, you need to rename this script to `jest.config.json`.
 
 There are also other analysis scripts available in `script` and `analyses` folder, which we used to produce the graphs for the paper. `scripts/data_factory.ipynb` includes a jupyter notebook which we used to produce most of the metadata for different npm modules and exploits. The notebook also contains necessary comments to reproduce the metadata and other required information.
diff --git a/ace-breakout/jest.config.json → ace-breakout/jest-analysis.config.json b/ace-breakout/jest.config.json → ace-breakout/jest-analysis.config.json
diff --git a/command-injection/babel.config.js → command-injection/babel-analysis.config.js b/command-injection/babel.config.js → command-injection/babel-analysis.config.js
diff --git a/command-injection/jest.config.json → command-injection/jest-analysis.config.json b/command-injection/jest.config.json → command-injection/jest-analysis.config.json
diff --git a/path-traversal/jest.config.json → path-traversal/jest-analysis.config.json b/path-traversal/jest.config.json → path-traversal/jest-analysis.config.json
diff --git a/prototype-pollution/babel.config.js → prototype-pollution/babel-analysis.config.js b/prototype-pollution/babel.config.js → prototype-pollution/babel-analysis.config.js
diff --git a/prototype-pollution/jest.config.json → ...otype-pollution/jest-analysis.config.json b/prototype-pollution/jest.config.json → ...otype-pollution/jest-analysis.config.json
diff --git a/redos/babel.config.js → redos/babel-analysis.config.js b/redos/babel.config.js → redos/babel-analysis.config.js
@@ -10,7 +10,9 @@ module.exports = function (api) {
   const presets = [];
   const plugins = [
     [require(`../prototype-pollution/babel-instrumentor.js`)],
-    [require("@babel/plugin-transform-modules-commonjs").default],
+    [require("@babel/plugin-transform-modules-commonjs").default, {
+      strictMode: false
+    }],
   ];
   const ignore = ["./require-interception.js"];
 

diff --git a/redos/jest.config.json → redos/jest-analysis.config.json b/redos/jest.config.json → redos/jest-analysis.config.json