Curating Secure Software: The Art of Selecting Safe Dependencies - Kadi McKean, ReversingLabs
Why It Matters
Because most applications rely heavily on third‑party packages, supply‑chain breaches that cross ecosystems and infiltrate CI can expose secrets and erode trust; organizations must strengthen vetting, provenance, and monitoring of direct and transitive dependencies to prevent operational and reputational damage.
Summary
Kadi (Katie) McKean, open source manager at ReversingLabs, framed selecting third-party dependencies as a curatorial process — start with clear requirements, assess acquisition and UX (how the code will be used), and evaluate impact. She warned that modern software is overwhelmingly composed of borrowed code and highlighted recent supply‑chain incidents (notably the Light LLM compromise that traversed npm to PyPI and infected CI pipelines) as examples of how malicious packages can exfiltrate secrets and propagate across ecosystems. McKean urged practitioners to go beyond CVE checks to consider tampering, provenance, signatures, secret exposure, and the risks posed by deep transitive dependency chains. She compared reputational and cultural fallout from compromised projects to the historical Isabella Stewart Gardner art heist to stress long‑term trust implications for maintainers and organizations.
Comments
Want to join the conversation?
Loading comments...