Joydeep Tripathy

@Dev-Voldemort , Not a Problem! I'll keep `perl`, `php` and `javascript` on my agenda for next week then.

Hello @tahifahimi , I already have the code ready for both of those, and for `perl` as well. Thank you for volunteering! There are a few issues which you could...

Agreed @Dev-Voldemort , I have all the scripts ready but they are not gonna be merged anytime soon (I think). Meanwhile, there are other issues to handle

Hello, - I'm thinking to design a separate database for integrating purl2cpe into our repo. Is this way of thinking correct? Or it would be more efficient to try and...

> We've got the first of our generated purl ids for the go parsers now: > > * [feat: added purl generation for go parser #3833](https://github.com/intel/cve-bin-tool/pull/3833) > > Folk interested...

Hello @terriko , I am interested in this project and will share an initial draft proposal on gitter soon!

@terriko @anthonyharrison I had a question. You have mentioned that step-2 would be integration of purl2cpe database into the language parsers. So since we are also going to have to...

> @joydeep049 I would plan to integrate the purl2cpe database first. I think you'll learn enough form integrating it that it'll result in a better design and integration setup for...

> And no, you're not really putting the de-dupe info in the language parsers I don't think? As @anthonyharrison indicated, you'll be putting the de-dupe info into a function that...

Only review and Merging left @terriko @anthonyharrison