3 ms·
I assume that's why they were acquired. At this point, they were a little bit more of a "feature" than a product. I suspect this tech is driving vuln alerts on
by lbotos 9y ago
I assume that's why they were acquired. At this point, they were a little bit more of a "feature" than a product. I suspect this tech is driving vuln alerts on repos:
https://github.com/blog/2470-introducing-security-alerts-on-github https://github.com/blog/2470-introducing-security-alerts-on-...
- dewey 9y ago> There, we’ll be working on expanding GitHub’s security tooling, like their recently announced vulnerable dependency alerting. You don't have to suspect, it's in the article :)
- phillmv 9y agoI would hate to take credit for work I didn't do, so I would just like to quickly set the record straight: We had nothing to do with that feature! We legit joined just now. But it certainly demonstrated a certain synergy between our skillset and GitHub's feature roadmap ;).
- ontoillogical 9y agoAlas, it’s in the future tense. We can’t take credit for the current security offerings - it was the work of our soon-to-be coworkers at GitHub.