> I meant to add: for the ones related to source analysis, what's needed
> are some unit tests.
>
Absolutely. My thoughts exactly. I thought that MUST be part of any PR I am
going to add - to add some unit tests - but I need to know where the
perception that something is wrong was from and get some examples so that I
can build the unit tests looking at those. I think there are many "you need
to add this and that' but three is very little ("because I saw it here an
there") - that could be helpful to validate if the issue is "valid" and
what "false-positive" it was based on. also because I would not be able to
validate if the issue is solved when I implement it. I have quite an
experience with automating GitHub Actions and testing and I might even add
automation around it as part of some first requests -but I would love some
good first issue I could work on that has some good data I can test it on.
