Software Composition Analysis

Software Composition Analysis, or SCA, identifies third-party components and checks them for known vulnerabilities, license risk, and supply-chain exposure.

What it means

Software Composition Analysis identifies the third-party components inside a project. It commonly checks manifests and lockfiles for vulnerable versions, risky licenses, and known supply-chain exposure.

Why it matters for AI-written code

AI-generated code can add dependencies casually. SCA helps teams see whether those additions create hidden obligations or vulnerabilities.

Guard and Fleet context

Guard folds SCA-style evidence into recurring dependency hygiene audits. Fleet views show repeated package risk across repositories, so teams can address shared exposure instead of treating every finding as isolated.

How Enji Guard helps

Guard surfaces dependency risk with context, points to affected project health, and prepares reviewable dependency updates when the change is bounded enough to verify.