package-analysis
package-analysis copied to clipboard
Obfuscation detection prototype
Currently this code can parse JS files or strings and print out statistics regarding string literal lengths and entropies, and identifier (function/variable/class names) lengths and entropies
I had it this way initially, but then the CI pipeline fails because the unit tests require calling the JS code. I'm not sure how to solve this - thoughts?
I had it this way initially, but then the CI pipeline fails because the unit tests require calling the JS code. I'm not sure how to solve this - thoughts?
Can we fix the CI pipeline to have it run npm install before running tests?