Updated changelog and usage

Author: Razican

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## SUPER 0.3.1
+
+### Bug Fixes
+
+- SUPER will now have `super-analyzer` as package name. This avoids conflicts with Debian
+  repositories.
+
 ## SUPER 0.3.0
 
 ### Features

README.md

@@ -58,22 +58,25 @@ FLAGS:
         --bench       Show benchmarks for the analysis
         --force       If you'd like to force the auditor to do everything from the beginning
     -h, --help        Prints help information
+        --html        Generates the reults in HTML format
+        --json        Generates the reults in JSON format
         --open        Open the report in a browser once it is complete
     -q, --quiet       If you'd like a zen auditor that won't output anything in stdout
     -a, --test-all    Test all .apk files in the downloads directory
     -V, --version     Prints version information
     -v, --verbose     If you'd like the auditor to talk more than necessary
 
 OPTIONS:
-        --apktool <apktool>        Path to the apktool file
-        --dex2jar <dex2jar>        Where to store the jar files
-        --dist <dist>              Folder where distribution files will be extracted
-        --downloads <downloads>    Folder where the downloads are stored
-        --jd-cmd <jd-cmd>          Path to the jd-cmd file
-        --results <results>        Folder where to store the results
-        --rules <rules>            Path to a JSON rules file
-        --template <template>      Path to a results template file
-    -t, --threads <threads>        Number of threads to use
+        --apktool <apktool>                    Path to the apktool file
+        --dex2jar <dex2jar>                    Where to store the jar files
+        --dist <dist>                          Folder where distribution files will be extracted
+        --downloads <downloads>                Folder where the downloads are stored
+        --jd-cmd <jd-cmd>                      Path to the jd-cmd file
+        --min-criticality <min_criticality>    Set a minimum criticality to analyze (Critical, High, Medium, Low)
+        --results <results>                    Folder where to store the results
+        --rules <rules>                        Path to a JSON rules file
+        --template <template>                  Path to a results template file
+    -t, --threads <threads>                    Number of threads to use
 
 ARGS:
     <package>    The package string of the application to test