Skip to content

Security: ericcornelissen/js-regex-security-scanner

SECURITY.md

Security Policy

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 2026-01-01. If you are reading this after that date you should try to find an up-to-date version in the official source repository.

Supported Versions

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

Version End-of-life
0.x.x -

This table only includes information on versions <1.0.0.

Reporting a Vulnerability

To report a security issue in the latest version of a supported version range, either:

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.

What to Include in a Report

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

Threat Model

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.

Advisories

NOTE: Advisories will be created only for vulnerabilities present in released versions of the project.

ID Date Affected versions Patched versions
- - - -

This table is ordered most to least recent.

Acknowledgments

We would like to publicly thank the following reporters:

  • None yet

There aren’t any published security advisories