3 ms·
Can you please clarify whether the fork also suffers from the same security issues (or engage the fork's owner to ensure that it doesn't https://github.com/t3do
by joshka 2y ago
Can you please clarify whether the fork also suffers from the same security issues (or engage the fork's owner to ensure that it doesn't https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you)
- isidorn 2y agoThanks for flagging it. Our security researchers will analize it and based on their findings we might remove this one as well.
- csears 2y agos/analize/analyze/g
- theo-steiner 2y agos/g/
- theobr 2y agoHi, owner of the fork here. I did a thorough combing of the code base when I forked. Just did another audit and still not seeing anything suspicious. Gutting all of the opencollective and changelog code to be 1000% sure.
- theobr 2y agoThe only potential risk was the use of sanity to render a changelog. I didn't want to risk it, so I gutted that and a ton of other stuff. Just published a new, stripped down version. https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you/pull/11 https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you/p...
- f272529 2y agoOk, but did you remove something that explicitly appeared malicious? This is a key detail that I am not seeing in your comments or commit messages.
- jorams 2y agoThat's covered by > I did a thorough combing of the code base when I forked. Just did another audit and still not seeing anything suspicious.
- maxloh 2y agoHi. Please do not replace the original author's copyright notice in the LICENSE file. That is a violation of the Apache License. You could instead "append" your name to the copyright notice though, which is legal. https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you/commit/9e66548c8cca908139e192ab45dbd91cbad6faab https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you/c...
- Der_Einzige 2y ago[flagged]