Yamale

Latest version: v5.2.1

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

Scan your dependencies

Page 2 of 4

4.0.0

Not secure
This release is created to address the following issue: https://github.com/23andMe/Yamale/issues/167

The change in PR https://github.com/23andMe/Yamale/pull/173 mitigates that specific issue. We are unaware of any backwards incompatibility with the introduction of this fix, but we wanted to increment the major version number in case there are users with more complex schemas than what we test again.

We've also included the following warning in our README:

> ⚠️ Ensure that your schema definitions come from internal or trusted sources. Yamale does not protect against intentionally malicious schemas.

3.0.8

Not secure
This release fixes a bug where a well-formed schema file can execute arbitrary code on the system running Yamale.

3.0.2

Not secure
Fixes 119, strict mode was not the default on the command line....but it was for the API. This fix ensures strict mode is the default in all uses.

3.0.0

Not secure
**Note**: Due to a packaging bug, users running Python 2.x should pin the major version of Yamale to 2.x.

We're doing a major version jump to include the following changes:
* Remove Python 2.x support
* Make the default validation "strict". The `--strict` command line is now replaced with `--no-strict` for those that want the old behavior. See the README for more details.
* Prevent int and num validators from accepting bool values. 109

2.2.0

Not secure
Ability to specify schema and data without a filename 104

2.1.0

Not secure
Removed the printing of stacktraces to the command line (83)
Add support for a "key" constraint to the "map" validator (95)
Make any() accept anything (93)
Empty data file should fail if schema requires something (81)
Add a check for an empty schema file (70)

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.