https://github.com/expressjs/security-wg
Express.js Security Working Group
https://github.com/expressjs/security-wg
Last synced: 3 months ago
JSON representation
Express.js Security Working Group
- Host: GitHub
- URL: https://github.com/expressjs/security-wg
- Owner: expressjs
- License: mit
- Created: 2024-03-04T00:19:45.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2025-01-28T13:51:59.000Z (12 months ago)
- Last Synced: 2025-01-28T14:42:46.276Z (12 months ago)
- Size: 50.8 KB
- Stars: 10
- Watchers: 16
- Forks: 5
- Open Issues: 19
-
Metadata Files:
- Readme: README.md
- Contributing: Contributing.md
- License: LICENSE
Awesome Lists containing this project
README
# Security Working Group
## Charter
The Security Working Group manages all aspects and processes linked to the Express Project's security.
The Security Triage Team is responsible for managing incoming security reports, to prepare security patches/releases, and to coordinate vulnerability disclosures. The nature of this task is sensitive, so only the Security Triage Team, TC members, and (impacted) Repo Captains are involved in the process.
### Responsibilities
- Define the Security triage role
- Define and maintain security policies and procedures for the project and the packages in scope (see [this table for scope details](https://github.com/expressjs/security-wg/blob/main/docs/packages-in-scope.md))
- Provide guidance to the ecosystem on how to build more secure middleware
- Review and recommend processes for handling of security reports.
- Promote improvement of security practices within the Express project's ecosystem (For example: [OSSF Scorecard](https://github.com/expressjs/discussions/issues/162), threat model, etc..)
- Recommend security improvements for the project and the packages in scope
- Support the TC team on security triage as needed
- Support initiatives from the [OpenJS Foundation Security Collab Space](https://github.com/openjs-foundation/security-collab-space).
- Support initiatives from the OpenSSF [Best Practices for Open Source Developers Working Group](https://github.com/ossf/wg-best-practices-os-developers).
## Current Initiatives
| Initiative | Champion | Status | Links |
|------------|----------|--------|-------|
| OSSF Scorecard | [@inigomarquinez](https://github.com/inigomarquinez) | In progress | [#2](https://github.com/expressjs/security-wg/issues/2)|
| Threat Model | _TBC_ | In progress | [#3](https://github.com/expressjs/security-wg/issues/3) |
## Members
The Security Working Group is composed of two groups of members: the Security Triage Team and the Regular members. The regular members are responsible for the public facing activity of the group, while the Security Triage Team is responsible for the security triage process.
### Security Triage Team @expressjs/security-triage
- [Carlos Serrano](https://github.com/carpasse)
- [Chris de Almeida](https://github.com/ctcpip)
- [Íñigo Marquínez Prado](https://github.com/inigomarquinez)
- [Jean Burellier](https://github.com/sheplu)
- [Jordan Harband](https://github.com/ljharb)
- [Jon Church](https://github.com/jonchurch)
- [Marco Ippolito](https://github.com/marco-ippolito)
- [Rafael Gonzaga](https://github.com/RafaelGSS)
- [Sebastian Beltran](https://github.com/bjohansebas)
- [Ulises Gascón](https://github.com/UlisesGascon)
- [Wes Todd](https://github.com/wesleytodd)
### Team Members @expressjs/security-wg
- [Carlos Serrano](https://github.com/carpasse)
- [Chris de Almeida](https://github.com/ctcpip)
- [Íñigo Marquínez Prado](https://github.com/inigomarquinez)
- [Jean Burellier](https://github.com/sheplu)
- [Jordan Harband](https://github.com/ljharb)
- [Jon Church](https://github.com/jonchurch)
- [Marco Ippolito](https://github.com/marco-ippolito)
- [Rafael Gonzaga](https://github.com/RafaelGSS)
- [Sebastian Beltran](https://github.com/bjohansebas)
- [Ulises Gascón](https://github.com/UlisesGascon) (Captain @expressjs/security-wg-captains)
- [Wes Todd](https://github.com/wesleytodd)
## Meetings
The Security Working Group meets on an ad hoc basis. The meeting is open to the public. The agenda and meeting notes are published in this repository. You can find the calendar entries in the [OpenJS Foundation calendar](https://openjsf.org/collaboration).
## Offline Discussions
The Security Working Group uses [GitHub issues](https://github.com/expressjs/security-wg/issues) for offline discussion. The discussions are open to the public and anyone may participate. Also, the group uses the channel `#express-security-wg` in the [OpenJS Foundation Slack](https://openjsf.org/collaboration) for realtime discussions.
## Code of Conduct
The [Express Project's CoC](https://github.com/expressjs/express/blob/master/Code-Of-Conduct.md) applies to this repo.