Skip to content

Code & Dependencies

This area covers your application’s own code and the open-source it depends on: static code analysis, data-flow analysis, dependency (software-composition) scanning, a generated SBOM, and license checks.

BenefitCapabilityBusiness value
Find code flawsCode security + code-flow analysisCatch vulnerabilities before they ship
Know your supply chainDependency (SCA) scanning + SBOMSee every component and its known risks
Stay compliantLicense scanningAvoid license violations in dependencies

The Code Security scanner inspects source for vulnerable patterns, and Code Flow Analysis traces how data moves through the code (a code-property-graph approach) to find issues that only appear along a path — surfacing exploitable flaws rather than surface-level matches.

Dependency Analysis identifies your open-source components and their known vulnerabilities. The SBOM Generator produces a Software Bill of Materials, and an enrichment step adds vulnerability and license context to each component.

The License Scanner flags dependency licenses that conflict with your policy, so legal/compliance risk is caught alongside security risk.

  1. Point the scanners at your repository or build (directly or via CI — see IaC Security for VCS/CI hooks).
  2. Review code findings and dependency vulnerabilities.
  3. Generate and store an SBOM for the build.
  4. Triage results in ASPM alongside cloud findings.
  • Generate an SBOM per release so you can answer “are we affected?” instantly when a new CVE lands.
  • Prioritize dependency vulnerabilities that are actually reachable in your code.