Clade

Latest version: v4.1

Safety actively analyzes 687881 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 10

3.4.3

* Store build exit code in configuration (`"build_exit_code"` field), which can be found in `conf.json` and `meta.json` files inside working directory
* Create `clade.log` file even when Clade is used through Python API

3.4.2

* Fix data corruption in get_root_cmds()

3.4.1

* Reduce memory footprint of PidGraph on huge projects
* Properly handle decoding errors of CIF console output

3.4

Clade 3.4 doesn't have a lot of changes from 3.3. New version mainly fixes performance regressions by changing the way data is stored.

Changes:
* Move back to storing data in separate json files: zip files proved to be too inconvenient to use
* Add ability to specify indent of json files in the Clade configuration. `"indent": 0` can save disk space, while `"indent": 4` is more human-readable. `4` is the default value
* pytest: skip tests that can't be run (tests that require CIF, for example)
* Add workaround for segmentation fault inside `ujson`
* Add preset `klever`

3.3.9

* Add ability to pass configuration as JSON string. Example: `clade --conf '{"CmdGraph.requires": ["CC", "LD"]}' make`
* Do not fail if `Callgraph` is empty (it is not always bad), only print warning message
* Fix an issue on Windows which prevented `SrcGraph` to calculate file sizes
* Add `yield_functions_by_file()` internal method required by Klever

3.3.8

* Support BitBake
* Attempt to respect other tools that can use `LD_PRELOAD` with Clade
* Add `Common.include_list` option to specify which commands you are interested in
* Store Clade launch command in meta.json
* Other small changes and improvements

Page 4 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.