README.md

Security Working Group

Charter

The Security Working Group manages all aspects and processes linked to Express.js security, and is responsible for managing incoming security reports, and responsible also to prepare patches or releases. The nature of this task is sensitive, so only the Security triage team, Repo Captains and TC members will be involved on it.

Responsibilities include

• Define the Security triage role
• Define and maintain security policies and procedures for the project and the packages in scope
• 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.js ecosystem (For example: OSSF Scorecard, 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.
• Support initiatives from the OpenSSF Best Practices for Open Source Developers Working Group.

Current Initiatives

We are currently defining the Initiatives for 2024, feel free to participate.

Initiative	Champion	Status	Links
OSSF Scorecard	@inigomarquinez	In progress	#2
Threat Model	TBC	In progress	#3
Support OSTIF Audit	@UlisesGascon	In progress	#6

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

• Adam Ruddermann
• Chris de Almeida
• Jean Burellier
• Marco Ippolito
• Rafael Gonzaga
• Ulises Gascón
• Wes Todd

Team Members

• Adam Ruddermann
• Carlos Serrano
• Chris de Almeida
• Íñigo Marquínez Prado
• Jean Burellier
• Marco Ippolito
• Rafael Gonzaga
• Ulises Gascón
• Wes Todd

Meetings

The Security Working Group meets every two weeks. Meetings are held on Zoom and are recorded or directly streamed to Youtube. The meeting is open to the public. The agenda and meeting notes are published in this repository.

Offline Discussions

The Security Working Group uses the GitHub issues for offline discussions. The discussions are open to the public and anyone can participate. Also, the group uses the channel #express-security-wg in the OpenJS Foundation Slack for real-time discussions.

Code of Conduct

The Express.js CoC applies to this repo.