The maintainers of the JavaScript Regex Security Scanner 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 2027-01-01. If you are reading this after that date, try to 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 a supported version or the development head of the project, either (in order of preference):

• Report it through GitHub, or
• Send an email to ericornelissen+security@gmail.com with the terms "SECURITY" and "js-regex-security-scanner" in the subject line.

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

If a security issue only affects an unsupported version of the project, or the latest version of a supported version range is not affected, please report it publicly. For example, as a regular issue in the public repository. If in doubt, report the issue privately.

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

The scanner considers Docker, ESLint, and its plugins to be trusted. All inputs are considered untrusted. Any violation of confidentiality, integrity, and availability is considered a security issue.

The project considers the GitHub infrastructure and all project maintainers to be trusted. Any action performed on the repository by any other GitHub user is considered untrusted.

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.

If you conduct a security audit of this project we would like to acknowledge it. If you found a security issue, you will be credited in the advisory. If you find nothing but the audit report is publicly available we will acknowledge it too.

We would like to publicly thank the following reporters:

• None yet