Software Composition Analysis: What's in Your Codebase
Build software composition analysis into CI with dependency inventories, vulnerability checks and licence review. Define owners, response targets and follow-up.

Last year, one of our dependencies had a critical vulnerability published on a Friday afternoon. The identifier cited in the original account, CVE-2025-32751, describes local sensitive-information disclosure in Dell PowerFlex Manager. It does not identify the JSON-parser incident described here; that incident’s identifier still needs confirmation. The fix took us 4 hours. But the real question was harder: how many of our 847 transitive dependencies were affected? We didn't know, because we'd never systematically inventoried what was in our codebase. That weekend I set up our first Software Composition Analysis (SCA) pipeline, and what we found was alarming.[1]
34% of our dependencies hadn't been updated in over 18 months. 11 had known vulnerabilities, 3 of them rated high severity. 2 were abandoned projects with no maintainer. And one dependency, pulled in transitively by a testing library, had a license that was incompatible with our commercial use.
This is the state of most codebases. Not because teams are careless, but because nobody's watching. SCA is how you start watching.
What Software Composition Analysis Actually Does
SCA tools inventory the components they can resolve from package manifests, lockfiles and other supported inputs, including direct and transitive dependencies. They compare that inventory with vulnerability and licence information. The code intelligence guide explains how this evidence fits alongside other codebase analysis.
The output is three things:
- A Software Bill of Materials (SBOM): A complete list of every component in your application, with versions.
- Vulnerability alerts: Known CVEs affecting your dependencies, with severity ratings and fix availability.
- License compliance report: What licenses govern your dependencies and whether any conflict with your distribution model.
NIST’s guidance under Executive Order 14028 recommends access to machine-readable SBOMs when applicable to a federal procurement action. The EU Cyber Resilience Act requires covered manufacturers to identify and document product components, including an SBOM in a commonly used machine-readable format. Most provisions apply from 11 December 2027, with some reporting duties applying earlier. Check the requirements applicable to the product and procurement.[2][3]
The Numbers That Should Scare You
I've run SCA scans across 8 production codebases over the past 2 years. Here's what I typically find:
- Average direct dependencies: 87 (Node.js), 43 (Python), 62 (Go)
- Average transitive dependencies: 634 (Node.js), 187 (Python), 118 (Go)
- Dependencies with known vulnerabilities: 4-12% of total
- Dependencies with no update in 24+ months: 18-31%
- License conflicts found: At least 1 per codebase
The Node.js numbers are the scariest. A typical Next.js application pulls in 800-1,200 transitive dependencies. That's 800+ pieces of code you didn't write, didn't review, and often don't know exist, all running in your production environment.
Building an SCA Pipeline
Here's how I set up SCA from scratch. The total implementation time is about 2-3 days for the initial setup, plus an ongoing 2-4 hours per week for triage.
Step 1: Choose Your Scanner
The SCA market has matured significantly. Here's my honest assessment of the options:
npm audit/pip-audit/govulncheck: These vulnerability tools cover different ecosystems and need appropriate installation and input. They can assess transitive dependency vulnerabilities; govulncheck also analyses calls to vulnerable functions. Their vulnerability output does not replace a licence review.- OWASP Dependency-Check: Free, covers multiple languages, integrates with CI. More thorough than built-in tools but slower and requires configuration.
- Trivy: My recommendation for teams starting out. Free, fast, covers vulnerabilities and some license checking, supports containers and IaC in addition to dependencies.
Commercial:
- Snyk: Offers IDE and pull-request integrations. Its published Free and Team options have product limits, and larger plans use custom pricing. Check the current plan for the required products and team size.
- Sonatype Nexus: Best for enterprise governance. Deep license analysis, policy engine. Pricing varies by org size.
- Mend (formerly WhiteSource): Strong on license compliance. Good for companies with strict IP requirements.
For most teams under 50 engineers, I recommend starting with Trivy (free) and graduating to Snyk if you need the developer workflow integration.
Step 2: Integrate Into CI
Configure the scanner and SARIF upload permissions together. Ensure that a failed scan still leaves its findings available for review.[7]
# Workflow file .github/workflows/sca.yml
name: Software Composition Analysis
permissions:
contents: read
security-events: write
on:
pull_request:
schedule:
- cron: "0 6 * * 1" # weekly Monday scan
jobs:
vulnerability-scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run Trivy vulnerability scanner
uses: aquasecurity/trivy-action@v0.36.0
with:
scan-type: "fs"
scan-ref: "."
severity: "HIGH,CRITICAL"
exit-code: "1" # fail the build on high/critical
format: "sarif"
output: "trivy-results.sarif"
- name: Upload results to GitHub Security
if: always()
uses: github/codeql-action/upload-sarif@v4
with:
sarif_file: "trivy-results.sarif"
license-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npx license-checker --production --failOn "GPL-3.0;AGPL-3.0"Step 3: Establish a Dependency Policy
Assign owners and response rules for scanner findings. Use dependency mapping to inspect where a component is used, and continuous quality monitoring to keep the findings visible over time.
The dependency policy I use:
Vulnerability response SLAs:
- Critical (CVSS 9.0+): Fix or mitigate within 48 hours
- High (CVSS 7.0-8.9): Fix within 1 sprint (2 weeks)
- Medium (CVSS 4.0-6.9): Fix within 1 month
- Low (CVSS <4.0): Fix during scheduled maintenance
New dependency approval criteria:
- Must have >500 GitHub stars or be from a recognized organization
- Must have a commit within the last 6 months
- Must use an approved license (MIT, Apache 2.0, BSD, ISC)
- Must not have any unpatched high/critical CVEs
Dependency update cadence:
- Security patches: applied within SLA above
- Minor versions: updated monthly
- Major versions: evaluated quarterly, updated when justified
The Contrarian Take
Most SCA advice says "update everything, all the time." I think that's wrong and actively counterproductive. Chasing every minor version update creates noise, introduces upgrade risk, and burns engineering time on work that delivers zero user value.
Here's my approach: I only update dependencies for three reasons. First, security vulnerabilities (following the SLA above). Second, when we need a feature from a newer version. Third, when the current version is approaching end-of-life. That's it.
I've seen teams spend 20% of their sprint capacity on dependency updates that weren't security-related and didn't unlock any new functionality. That's a full day per engineer per week spent on gardening that doesn't make the product better. Pin your versions, monitor for security issues, and update only when there's a concrete reason.
The Stealable Framework: Monthly SCA Review
Schedule a 1-hour monthly meeting with this agenda:
First 15 minutes: Dashboard Review
- Total dependencies (trending up? Question new additions)
- Open vulnerability count by severity
- Average age of dependencies
Next 20 minutes: Critical Items
- Any new high/critical CVEs since last review
- Dependencies approaching end-of-life
- License issues
Next 15 minutes: Policy Compliance
- Were all vulnerability SLAs met last month?
- Were any unapproved dependencies added?
- Any dependency requests pending review
Last 10 minutes: Action Items
- Assign owners for each open item
- Set deadlines
- Update the dependency policy if needed
After 6 months of running this cadence, our mean time to remediate critical vulnerabilities dropped from 11 days to 2.3 days. Not because we got faster at patching, but because we caught issues earlier and had a process for prioritizing them.
Your codebase is mostly other people's code. Knowing what's in it, whether it's safe, and whether it's maintained isn't paranoia. It's basic operational hygiene.
Frequently asked questions
Does npm audit check transitive dependencies?
npm audit processes the dependency tree and calculates vulnerabilities and meta-vulnerabilities from advisory information. Check the lockfile and omitted dependency types, since scanner coverage depends on the input and configuration.
Does an SBOM prove that software is secure?
An SBOM records components and their versions. Use it with vulnerability information and an assessment of the deployed application, then assign remediation work through the team’s response process.
Are vulnerability and licence checks the same scan?
Tools can support both, but the findings answer different questions. A vulnerability finding concerns a known security issue, while a licence finding needs review against the software’s actual use and distribution.
How should we prioritise dependency findings?
Review the severity, affected version and the application’s exposure, then identify a fix or mitigation and an owner. The article’s response times are an example team policy that needs to fit the system and its obligations.
Sources
- [1]NVD-CVE-2025-32751 · NIST National Vulnerability Database
- [2]Software Security in Supply Chains: Software Bill of Materials (SBOM) · NIST
- [3]Regulation - 2024/2847 - EN - EUR-Lex · European Union
- [4]npm-audit | npm Docs · npm
- [5]GitHub - pypa/pip-audit: Audits Python environments, requirements files and dependency trees for known security vulnerabilities, and can automatically fix them · Python Packaging Authority
- [6]Go Vulnerability Management - The Go Programming Language · Go
- [7]GitHub - aquasecurity/trivy-action: Runs Trivy as GitHub action to scan your Docker container image for vulnerabilities · Aqua Security
Checked against these sources on





