Thomas.G

icon company @OpenAlly icon location Paris icon location French Node.js freelancer with 10+ exp @nodejs Security Collaborator. @NodeSecure, @OpenAlly, @TopCli core maintainer.

Results 69 comments of Thomas.G

Add UT around probes

List of probes that still need contribution. > **Note** > Please contribute and create merge request for one probe at a time. Already done: - [x] isLiteralRegex (contributed by @fraxken)...

Missing Interceptable type in export ?

I'm ok to send a PR if maintainer confirm this should be exported :)

Enhance 'summary' CLI command

Ok a first version of the summary command has been merged in master. Any feedbacks are welcome. All that's missing now is the warnings.

Reaching out to other projects of the OpenJS Foundation

@MarcinHoppe can we close the issue ?

Publicizing information about packages using deprecated/insecure buffer APIs

@sam-github Do you still plan to do something or should we close this issue ?

What security guidance would be most useful for Node.js developers?

I think we are recently moving toward that goal. The idea is to use the work on the [threat model](https://github.com/nodejs/security-wg/issues/799) as a foundation for a new user documentation (which will...

Secure Node

👋 Hello, Some work is currently happening here: https://github.com/nodejs/security-wg/issues/791 I guess it will solve some of the concerns raised by this old issue/proposal.

Write first draft of responsible security reporting guidelines for OpenJS Foundation

👋 Is the subject still relevant? I see that some work has been done on the OpenJS side but I have trouble understanding everything. I remember we add some Responsible...

Include publishing a GitHub Security Advisory in the triage process

Interesting topic. Any news on this? There are probably things that have evolved in two years! Today github seems to me quite efficient at reporting CVE, no? (However I never...

Fuzzing Node.js core

@vdeturckheim Is this still an active subject?