That's not the conclusion I have. The code is corrected and even if you don't trust the dev, the code is open and problems can be detected. It would be a problem if the developer did not acknowledge and correct the problem. It's 2 years ago and since then there wasn't an issue. But everyone can decide for themselves, I'm just speaking for myself.

[–] ivn@jlai.lu 2 points 2 months ago* (last edited 2 months ago)

While the code being open is good you still have to rely on trust.

I certainly don't have the time to review to code of each extension I use. And even then, we have no garanties that the extension distributed through the browser stores has the same code.

You can see the issue was opened on august 18th but the responsible commit was only made on the 19th. So the code was pushed the extension users before it was made available on the repository. Open code is of no help here.