Folder	Description
`src`	Source
`src_dataset`	Source for batch cloning public repositories
`test_src`	Example targets for development
`output`	Webpack-ed dependencies
`dist`	Sliced dependencies

How to rerun the program

Collect the mineable repositories
```
node src_dataset/index.mjs
```
Look at the code and you can tweak the number of repos that are being used.

They will get copied to ../cache-repos/repos. package.json of each of the files are fetched from npm (so that we dont clone the whole repo) and cached in ../cache-repos.
Get a list of candidate repos that can slice.
```
./script.sh
```
If something goes wrong, add it to the ignore list. This also moves the repos into a candidates/ folder. It will create success.txt with a list of repos that work with slicing.
Slice and get test results

Go through success.txt, and run master.sh with each repo.

./master.sh cov -> Get test coverage and pre-test count ./master.sh exec -> Slice and post coverage ./master.sh cloc -> Sliced statistics

Note that in some cases, the scripts may attempt to execute tests in the backup node modules folder (.node_modules). In this case, move it out, and run the tests individually. You can get the commands from the output from the master script (which calls the script-placer.sh script).

Vuln finding

The scripts here help find repositories that are - firstly, slicable, and have a direct dependency on a repo that have a github advisory (~CVE) on them.

From there, you can run the slicer manually to track if they get removed.

Note that it uses the success.txt, not output.