1. Why Debloating Third-Party Software?
    • The Log4j vulnerability is an example of the dangers of massively reusing third-party libraries. This article discusses how software debloating can make a difference by reducing the attack surface of applications, removing unnecessary code from software libraries.

  2. Diversity-Driven Software Debloat
    • I leverage the diversity of code coverage tools to create a tool to automatically debloat Java artifacts.

  3. Unnecessary Code
    • Unnecessary code is such that can be deleted from the codebase without affecting the expected functionality of the software project.