Allen D. Householder
Allen D. Householder
We're tagging vul IDs (more than just CVE) at - https://github.com/CERTCC/exploitdb - https://github.com/CERTCC/metasploit-framework We pull updates from their respective repositories every few hours, crawl the diffs for IDs we recognize,...
> * https://github.com/CERTCC/labyrinth/ by @ahouseholder now has a license and already aggregates the above. Just to set expectations on data quality: Please be aware of the notes about signal-to-noise in...
On the other hand, we're more confident about the exploitdb/metasploit tags indicating exploits because there's a human vetting process involved (i.e., their developers decide what to include in their product).
Test data blobs added for the two new activities in commit b2c2dc0
Finally got it right. :-)
See also #17. Worth keeping this issue in mind when implementing that.
The treeless clone idea in https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/ might be relevant to solve this.
This might be a duplicate of #7
I have a demonstration of the branch -> do work -> squash-merge -> delete branch workflow in https://github.com/ahouseholder/stunning-umbrella
Checkout time is running around 40 minutes now.