https://github.com/feross/security

Security Policies and Procedures for @feross projects
https://github.com/feross/security

disclosure javascript nodejs policy report security

Last synced: 13 days ago
JSON representation

Security Policies and Procedures for @feross projects

• Host: GitHub
• URL: https://github.com/feross/security
• Owner: feross
• Created: 2019-03-26T05:17:24.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2019-03-26T05:20:27.000Z (almost 6 years ago)
• Last Synced: 2025-01-03T02:53:01.152Z (17 days ago)
• Topics: disclosure, javascript, nodejs, policy, report, security
• Homepage: https://feross.org
• Size: 1.95 KB
• Stars: 14
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Security Policies and Procedures

This document outlines security procedures and general policies for

[@feross](https://github.com/feross) projects.

  * [Reporting a Bug](#reporting-a-bug)

  * [Disclosure Policy](#disclosure-policy)

  * [Comments on this Policy](#comments-on-this-policy)

## Reporting a Bug

Feross takes all security bugs in his projects seriously. Thank you for

improving the security of Feross's projects. 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, the security team 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.

## Disclosure Policy

When the security 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.