Skip to content

Latest commit

 

History

History
43 lines (31 loc) · 1.71 KB

SECURITY.md

File metadata and controls

43 lines (31 loc) · 1.71 KB

Security Policies and Procedures

This document outlines security procedures and general policies for the Ramda Adjunct project.

Reporting a Bug

The Ramda Adjunct team and community take all security bugs in Ramda Adjunct seriously. Thank you for improving the security of Ramda Adjunct. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.

Report security bugs by emailing the lead maintainer at [email protected].

The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, one of the team members will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

Report security bugs in third-party modules to the person or team maintaining the module, but still let us know that we have such a third-party module in our dependencies.

Disclosure Policy

When the team receives a security bug report, they will assign it to a primary 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 be released as fast as possible to npm.

Comments on this Policy

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