Prospector

Latest version: v1.16.1

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

Scan your dependencies

Page 2 of 16

1.9.0

-------------

* https://github.com/PyCQA/prospector/pull/577
* https://github.com/PyCQA/prospector/pull/580
* https://github.com/PyCQA/prospector/pull/592

1.8.4

-------------

* https://github.com/PyCQA/prospector/issues/566
* https://github.com/PyCQA/prospector/issues/575
* https://github.com/PyCQA/prospector/issues/578

1.8.3

-------------

* `560 <https://github.com/PyCQA/prospector/issues/560>`_
* `559 <https://github.com/PyCQA/prospector/issues/559>`_
* `555 <https://github.com/PyCQA/prospector/issues/555>`_
* `554 <https://github.com/PyCQA/prospector/issues/554>`_
* `552 <https://github.com/PyCQA/prospector/issues/552>`_
* `551 <https://github.com/PyCQA/prospector/issues/551>`_

1.8.2

-------------

* `547 <https://github.com/PyCQA/prospector/issues/547>`_

1.8.1

-------------

Let's test faster.

**Add support for Python 3.11**:

Python 3.11 is between 10-60% faster than Python 3.10.

1.8.0

-------------

**File discovery fixes**:

Finding paths and files to check has been replaced with a new version using ``pathlib`` - this should not result in any changes,
except fixing an issue where ``pylint`` and ``pydocstyle`` were inspecting the same file or directory twice sometimes.
However it may cause slightly different orders or reduce these duplicate warnings.

The behavior of prospector should be unchanged, apart from some bugfixes related to the old file discovery mechanism.

Related bugs and PRs:

* `480 <https://github.com/PyCQA/prospector/issues/480>`_
* `417 <https://github.com/PyCQA/prospector/issues/417>`_
* `199 <https://github.com/PyCQA/prospector/issues/199>`_

**Other bugfixes**:

* `106 <https://github.com/PyCQA/prospector/issues/106>`_
* Running prospector on a path not in the CWD (eg, 'prospector /some/where/else') will not cause exceptions, and will instead use absolute paths for message output
* Autodetction of libraries, to automatically use pylint plugins, will no work on projects using a pyproject.toml ; also it has been turned on by default, it seemed to have accidentally been set to off by default some time ago.
* `529 <https://github.com/PyCQA/prospector/issues/529>`_

**Misc**:

* Prospector now runs on itself without generating errors after all linting warnings were fixed

Page 2 of 16

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.