+ To be clear, this tool does not solve the problem if you are one of the first people to get infected; it minimizes your chance if you are the N-th person
159 karma · joined May 23, 2022
Building https://www.vidocsecurity.com/
Find me at: - https://x.com/kannthu1 - https://www.linkedin.com/in/dawid-moczadlo/
+ To be clear, this tool does not solve the problem if you are one of the first people to get infected; it minimizes your chance if you are the N-th person
So the claim that OSS models can find those zero-day issues was a lie.
I prefer writing high-quality content (posts) instead of commenting. It is not in my nature to write comments (and this style of contributing).
It does not mean that I am not putting high effort into writing posts - quite the opposite. When I write long content I put all my heart into it and many hours.
What I mean is that I would love to meaningfully contribute and gain karma by doing "content" the way I like and prefer and not being forced to comment.
You are right with the self-hosted version
I am a co-founder of https://vidocsecurity.com/ - one of our main features is validating security issues. To validate the security issue you need to find relevant context - let's say we detected a potential security issue in file "test.ts" in function "doStuff". We would need to find what other functions in the repository reference this function and do it recursively to build a call tree. Then we use LLM to validate each branch of the tree to understand if the issue could be exploitable.
It took me a couple of months to solve the context fetching and I managed to solve it in a way that is really easily extendable to other languages. At this moment we support Typescript, JS, Python, Go, Ruby, and Rust. I can add many more languages.
I talked with other founders and understood that what I built might be valuable to other companies as they rely on supporting as many languages as possible. This post is my attempt to understand if it is a real problem or if I just imagined it myself.