Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update security and performance best practices #1466

Open
crandmck opened this issue Mar 4, 2024 · 2 comments
Open

Update security and performance best practices #1466

crandmck opened this issue Mar 4, 2024 · 2 comments

Comments

@crandmck
Copy link
Member

crandmck commented Mar 4, 2024

This is a reminder to review these topics in light of the changes originally proposed in #1004 from @wesleytodd, which I closed due to extensive merge conflicts (it was 5+ years old).

If the fundamental changes in that PR are worth preserving, then let's open a new PR. If not, then we can close this, but I didn't want to just toss out the work since it covers some important topics.

@wesleytodd
Copy link
Member

Oh wow I forgot about this one! I wonder if we should also split this into two and hand the security docs over to the @expressjs/security-triage team?

@UlisesGascon
Copy link
Member

I wonder if we should also split this into two and hand the security docs over to the @expressjs/security-triage team?

Sounds like we can work on it and propose a PR. I will add it to the initiatives expressjs/security-wg#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants