A Decade Of Infosec Tools
summary
Quantitative analysis of 2000+ InfoSec projects pulls metadata from four publication sources and GitHub and shows a surprising GitHub monopoly (thousands of repos vs hundreds elsewhere), median project attention measured in low stars/forks and roughly median maintenance ~2.5 years, and scant community contributions (median ~4 pull requests, ~15 open issues). Python dominates with common deps like requests and Flask, and a risky reliance on PyCrypto still common; full dataset and reproducible workflow are published.
AI-written summary · about
chapters (4)
- 0:00Start
- 14:14How Long Is a Infosec Tool Maintained
- 26:20Best Choice for Crypto Module in Python
- 31:19Conclusion
related talks
43mThe Importance of Developer Tooling to Make Open Source More Secure by Default
54mUsing developer-centric data to improve Application Security Outcomes
32mExemplars, Laggards, and Hoarders: A Data-driven Look at Open Source Software Supply Chains
47m11,000 Voices: Experts Shed Light on 4-Year Open Source & AppSec Survey
45mExemplars, Laggards, & The Cautious: A Data-driven Look At High-velocity Software...
19mFlipping the script on application security
49mQuantifying the Probability of Flaws in Open Source
13mKeynote: Hacking the OSS Supply Chain