Prospector

Latest version: v1.16.1

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

Scan your dependencies

Page 12 of 16

0.9.8

---------------
* Fixing a crash when using pep8 1.6.0 due to the pep8 tool renaming something that Prospector uses

0.9.7

---------------
* `104 <https://github.com/PyCQA/prospector/issues/104/>`_ The previous attempt at normalising bytestrings and unicode in Python 2 was clumsily done and a bit broken. It is hopefully now using the correct voodoo incantations to get characters from one place to another.
* The blender combinations were not updated to use the new PyFlakes error codes; this is now fixed.

0.9.6

---------------
* The profile validator tool was always outputting absolute paths in messages. This is now fixed.
* The " NOQA" checking was using absolute paths incorrectly, which meant the message locations (with relative paths) did not match up and no messages were suppressed.

0.9.5

---------------
* Fixed a problem with profile serialising where it was using the incorrect dict value for strictness

0.9.4

---------------
* The previous PEP257 hack was not compatible with older versions of pep257.

0.9.3

---------------
* The PEP257 tool sets a logging level of DEBUG globally when imported as of version 0.4.1, and this causes huge amounts of tokenzing debug to be output. Prospector now has a hacky workaround until that is fixed.
* Extra profile information (mainly the shorthand information) is kept when parsing and serializing profiles.

Page 12 of 16

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.