[SEC-WG] Audit for Webpack?
@UlisesGascon is already working on this.
Since Jan 9, 2026.
Assessment
This issue has not been assessed yet.
Description
To separate topics from webpack/working-groups#9, I’m opening this.
It might be interesting to have an audit to find vulnerabilities. For example, Express did this a long time ago (https://expressjs.com/2024/10/22/security-audit-milestone-achievement.html
). In Express’s case, it was done through https://ostif.org/
and funded by Sovereign Tech Agency. We could try to achieve the same.
Now that we have a triage team, this seems like a good idea
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from webpack/working-groups
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 25/100
webpack/working-groups#10 ·
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
webpack/working-groups#11 · 2 comments ·
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
webpack/working-groups#12 · 2 comments ·
-
tsc-agenda
Difficulty 4/5 3-5 days Newbie friendliness 42/100
webpack/working-groups#13 · 1 comment ·
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
webpack/working-groups#1 · 2 comments ·