Validb

Latest version: v0.0.6

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

Scan your dependencies

0.0.6

💥 Breaking Changes
* Change command options `-r`/`--rules`, which specify configuration files, to `-c`/`--config`.
* Each Rule in the configuration file now requires the class name to be specified.
* `validate_db` now requires a set of available Embedders and their names as arguments. ()
* Changed to pass Embedder names instead of Embedder to Rule instances.
* Some classes are moved to other modules;
* `SQLAlchemyRule`, `SimpleSQLAlchemyRule` are now in module `validb.rules.sqlalchemy`
* `SQLAlchemyDataSource ` is now in module `validb.datasources.sqlalchemy`

✨ New Feature
* When an error is detected during command execution, the number of cases for each detection_type is totaled and output to the standard output.
* When embedding a variable in a message, an empty string is now embedded instead of an error if the variable is missing.

0.0.5

0.0.4

💥 Breaking Changes
* Removed a method of Detect to create the CSV row; From now on, use `validb.csvmapping.DetectionCsvMapping`.
* Renamed class `Row` to `DetectedVariables`; Accordingly, the argument names of functions implemented in Detected, Rule, and Embedder have been changed.

🐛 Bug Fix
* Fixed a bug where higher level anomalies were put off and not detected when the detection limit was exceeded.

✨ New Feature
* You can use custom DetectionCsvMapping, which create CSV rows according the detections; This means that you can customize the CSV columns.
* Variables at the time of detection can be used in the CSV output, as well as variables embedded by Embedder.

**Full Changelog**: https://github.com/unaguna/validb/compare/v0.0.3...v0.0.5

0.0.3

💥 Breaking Changes
* renamed `msg_type` to `detection_type`
* constructors `Rule` and `Detected` need an argument `level: int`
* Structure of rules.yml has been changed; root value is an object which contains keys `rules`, `embedders` (optional), and `datasources` (optional).
* Each Rule must have `datasource`, the name of data source which provide data to validate, such as engine of SQLAlchemy.

**Full Changelog**: https://github.com/unaguna/validb/compare/v0.0.2...v0.0.3

0.0.2

**Full Changelog**: https://github.com/unaguna/validb/compare/v0.0.1...v0.0.2

0.0.1

Links

Releases

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.