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
Activity
bjohansebas commentedon Jan 14, 2026
For posterity, @UlisesGascon submitted the form to see if we are accepted by the STA to be audited.
UlisesGascon commentedon Feb 23, 2026
No news so far, I will try to contact the team directly 👍
evenstensberg commentedon Aug 10, 2026
status awaiting @UlisesGascon input
evenstensberg commentedon Sep 7, 2026
status: @UlisesGascon & @bjohansebas will work on auditing.
UlisesGascon commentedon Sep 11, 2026
I think that we can run https://github.com/alpha-omega-security/scrutineer/ against our repos and collect potential vulnerabilities and triage them.
evenstensberg commentedon Sep 11, 2026
@UlisesGascon how are results outputted using this?
UlisesGascon commentedon Sep 11, 2026
The project is evolving super fast, but Security scanning my own code with Scrutineer and local coding models and Scrutineer: Scanning Open Source Without Flooding Maintainers can provide ton of context :)
bjohansebas commentedon Sep 12, 2026
At the moment I have access to Codex, and possibly Codex for security as well (I’m not sure if that was enabled for me) but we could use that too.