SECURITY.md

This document outlines security procedures and general policies for the Expressproject.

• Reporting a Bug or Security Vulnerability
• Disclosure Policy
• Comments on this Policy

The Express team and community take all security vulnerabilities seriously.Thank you for improving the security of Express and related projects.We appreciate your efforts in responsible disclosure and will make every effortto acknowledge your contributions.

ASecurity triage team memberorthe repo captainwill acknowledge your report as soon as possible.These timelines may extend when our triagevolunteers are away on holiday, particularly at the end of the year.

After the initial reply to your report, the security team willendeavor to keep you informed of the progress towards a fix and fullannouncement, and may ask for additional information or guidance.

The preferred way to report security vulnerabilities is throughGitHub Security Advisories.This allows us to collaborate on a fix while maintaining theconfidentiality of the report.

To report a vulnerability(docs):

1. Visit theSecurity tab of the affected repository on GitHub.
2. ClickReport a vulnerability and follow the provided steps.

This process applies to any repositories within the Express ecosystem.If you are unsure whether a repository falls under this policy,feel free to reach out via email.

If you prefer, you can also report security issues by emailingexpress-security@lists.openjsf.org.

To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.

The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.

If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.

When the security team receives a security bug report, they will assign it to aprimary handler. This person will coordinate the fix and release process,involving the following steps:

• Confirm the problem and determine the affected versions.
• Audit code to find any potential similar problems.
• Prepare fixes for all releases still under maintenance. These fixes will bereleased as fast as possible to npm.

If you have suggestions on how this process could be improved please submit apull request.

There aren’t any published security advisories