v0.2.0

Polystat v0.2.0

This release introduced the following changes:

• The --to console cli argument was removed. Instead, the results of the analysis are printed to console by default. To disable printing the results to console, use the new --quiet flag (-q for short).
• Added a decent-looking pretty-printer of the analysis results to console.
• j2eo was updated to 0.6.0
• py2eo was updated to 0.23.0

v0.1.12

Polystat v0.1.12

This release introduced the following changes:

• odin was updated to v0.4.5. This change allows the detection of the Direct State Access defects.
• py2eo was updated to v0.0.14.
• polystat-cli:
  • The generated SARIF output was changed slightly to be viewable with the VSCode SARIF extension. (thanks to @br4ch1st0chr0n3)
  • The output directories and temporary directories that were specified either on the command line or in the config file are now created automatically if they don't exist.

v0.1.11

Polystat v0.1.11

In this release polystat-cli is published to Maven Central! We have also added a coursier descriptor to the repository so that polystat-cli can be installed and managed by coursier! To install polystat-cli with coursier, run the following command:

cs install --channel https://raw.githubusercontent.com/polystat/polystat-cli/master/coursier/polystat.json polystat

After that you should be able to just run polystat-cli as follows:

$ polystat -v
...
polystat-cli = 0.1.11
...

Besides, the analysis procedure is no longer run if the filtering options (i.e. excludeRules / includeRules) exclude all the analyzers. Instead, a warning message is printed:

WARNING: The 'includeRules' key with values "liskov" excludes all the analyzers, so none were run!

v0.1.10

Polystat v0.1.10

This release mostly changes the structure of the files of the tmp directory.
The following changes were made:

• The generated .eo code goes into the tmp/eo subdirectory.
• The .xml XMIR files generated by EO parser from FaR analyzer go into the tmp/xmir subdirectory.
• The code read from stdin is written to tmp/stdin.<ext> where ext is the relevant extension (.eo for EO files, etc.)
• The code read from a single file is copied to tmp/singleFile/<filename>

v0.1.9

Polystat v0.1.9

This release addressed the usability of the --version option, in particular:

• In addition to the version of the polystat-cli itself, polystat --version also prints the following:

  • j2eo version (the one when no --j2eoVersion is specified)
  • py2eo version
  • odin version
  • far version

• The names of downloaded j2eo jars now include the version downloaded, e.g. j2eo-v0.5.3.jar.

• The --version commandline option now has a shorter alternative -v, so that polystat --version and polystat -v are equivalent.

Besides, the names of analyzers where changed according to needs of @APotyomkin. You may want to update the config files. To avoid the confusion when using the non-existent keys in includeRules or excludeRules, a helpful warning message was introduced:

WARNING: The analyzer with the key 'funny' does not exist. Run 'polystat list' to get the list of the available keys.

v0.1.8

Polystat v0.1.8

This release added a FaR analyzer to Polystat CLI. In addition, the following problems were addressed:

• Paths to files in .sarif.json files should be generated correctly now.
• Output and temporary directories that are specified are created if they don't exist.
• Analyzers names printed by polystat list and the ones used in .sarif.json files are now consistent (and shorter). They can also be changed easily if necessary. The analyzer names can be found by running:

java -jar polystat.jar list

• Using odin v0.4.3 (with better support for J2EO output).

v0.1.7

Polystat v0.1.7

• Fixed a bug which caused the CLI to crash when analyzing an empty directory with J2EO.
• Fixed generation of the aggregated SARIF output. Now it generates a single sarifLog object with a run object for each of the files it was run on. The file location can be found at sarifLog.runs[i].artifacts[0].location.uri.

v0.1.6

Polystat v0.1.6

In this release:

• --files option was renamed to --to. Its functionality was extended to account for more cases. See README.md for more information.

• a --j2eo-version was added, that specified which version of J2EO should be downloaded (if the download happens)

• Before writing to the output directory, its contents are cleaned up to avoid confusing the output from the analyzer with files from previous runs residual files.

v0.1.5

Polystat v0.1.5

In this release the Polystat CLI was updated to use the latest version of j2eo (0.5.0).
Also, py2eo integration was updated to produce EO objects with valid names.

WARNING: This release does not have binaries because some of the Scala 3 libraries are not
compatible with Native Image.

v0.1.4

Polystat v0.1.4

In this release the py2eo project was integrated into polystat-cli. You can now run:

polystat py --in python_files

...to analyze a directory with a bunch of python files. For more options and explanations, run:

polystat --help

or

polystat list --config

if you want to use the config file.