The Process (Roughly)
A software composition analysis process can become complex but always includes four phases: Scan, Analyze, Remediate, Repeat.
Scan
Scanning is the manual or automated process of learning what external components (dependencies) exist in your software. Sometimes a programming language ecosystem will have build and packaging best practices that can make it easier to learn about the first-order (direct) dependencies in the software. For instance, software written in the Ruby programming language usually lists its direct dependencies in a file called Gemfile. The Java programming language community regularly uses the Apache Maven tool to build the software and manage dependencies.
Packaging tools like these can make it easier ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access