The maintainers of the depreman project take security issues seriously. We appreciate your efforts to responsibly disclose your findings. Due to the non-funded and open-source nature of the project, we take a best-efforts approach when it comes to engaging with security reports.

This document should be considered expired after 2025-06-01. If you are reading this after that date you should find an up-to-date version in the official source repository.

The table below shows which versions of the project are currently supported with security updates.

To report a security issue in the latest version of a supported version range, either (in order of preference):

• Report it through GitHub, or
• Send an email to [email protected] with the terms "SECURITY" and "depreman" in the subject line.

Please do not open a regular issue or Pull Request in the public repository.

To report a security issue in an unsupported version of the project, or if the latest version of a supported version range isn't affected, please report it publicly. For example, as a regular issue in the public repository. If in doubt, report the issue privately.

Consider if the issue you found really is a security concern. Below you can find guidelines for what is and is not considered a security issue. Any issue that does not fall into one of the listed categories should be reported based on your own judgement. If in doubt, report the issue privately.

Any issue that is explicitly out of scope can still be reported, but should be reported publicly because it is not considered sensitive.

• Bugs with a security implication that can be triggered through inputs not provided by the user invoking the software.
• Insecure suggestions or snippets in the documentation.
• Security misconfigurations in the continuous integration and delivery pipeline or software supply chain.

• Insecure defaults or confusing API design.
• Known vulnerabilities in third-party dependencies or devDependencies.

Try to include as many of the following items as possible in a security report:

• An explanation of the issue
• A proof of concept exploit
• A suggested severity
• Relevant CWE identifiers
• The latest affected version
• The earliest affected version
• A suggested patch
• An automated regression test

An advisory will be created only if a vulnerability affects at least one released versions of the project. The affected versions range of an advisory will by default include all unsupported versions of the project at the time of disclosure.

All advisories are listed in the table below, ordered most to least recent by publication date.

We would like to publicly thank the following reporters:

• none yet