liveBook · Manning

Dependency scan

As explained in AI Governance

Dependency scanning is the automated examination of software dependencies to identify known vulnerabilities, licensing issues, or unapproved components.

Dependency scanning automatically checks software dependencies for known vulnerabilities. In ClaimAssist, security concerns about widely used AI libraries prompted the team to add scans to its CI pipeline. section 4.9

ClaimAssist supply-chain controls

The team had captured direct dependencies but not transitive ones. Alongside scanning, it began maintaining a lightweight software bill of materials for AI-specific components and established an internal package repository. section 4.9

How AI Governance covers it

How deep it goes
Describes adoption and an inventory gap, but specifies no scanner, coverage settings, or remediation workflow.
Examples
Uses ClaimAssist’s missing transitive dependency inventory and concerns about vulnerable AI libraries as the adoption case.
What you can do after
Apply dependency scanning in CI as a supply-chain control for software dependencies.
How it connects
Pairs dependency scanning with secret scanning, a software bill of materials, and an internal package repository.

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 AI Governance. The section links point to the parts of the book it draws on.