liveBook · Manning

Dependency scan

As explained in Grokking Software Architecture

Dependency scanning is the automated inspection of software dependencies for known vulnerabilities, malicious changes, or policy violations.

Dependency scanning checks an application’s third-party libraries against a database of known vulnerabilities. In a CI/CD pipeline, a scanner can read a Software Bill of Materials (SBOM)—a machine-readable inventory of dependencies—and halt deployment if a library is flagged as compromised. section 11.7.1

When a tiny dependency disappears

The left-pad package was only 11 lines long, yet thousands of projects depended on it. Its removal caused millions of automated builds to fail. The incident was not a malicious attack, but it exposed how fragile software supply chains can be. section 11.7.1

How Grokking Software Architecture covers it

How deep it goes
Defines SBOM-based vulnerability checks and deployment halts, but does not detail scanner configuration.
Examples
Uses the left-pad removal and resulting build failures to illustrate supply-chain fragility.
What you can do after
Operate/configure CI/CD checks to compare an SBOM with known-vulnerability data and halt flagged deployments.
How it connects
Connects software bills of materials, CI/CD pipelines, and vulnerability databases.

Also explained in

Compare how 2 books explain dependency scan →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.