1 Untracked OSS Licenses and Unpatched Transitive Deps
Software Composition Analysis (SCA) goes beyond vulnerability scanning to cover legal compliance and comprehensive dependency visibility.
License compliance risks:
- GPL/AGPL: Using GPL code in a commercial product may require open-sourcing your own code
- LGPL: Dynamic linking is generally OK but requires providing the LGPL library in modifiable form
- Copyleft propagation: Transitive GPL dependencies can affect your license obligations
Example license chain issue:
npm ls --all | grep license-check
# Your app uses: lodash (MIT) — OK!
# But a dependency uses: some-lib (GPL-3.0) — Risk!
license-checker --production --onlyAllow 'MIT;Apache-2.0;BSD-2-Clause;BSD-3-Clause'
# Exit code 1 if any dependency has a disallowed licenseUnpatched transitive dependencies:
You might update all direct dependencies to patched versions but still have transitive dependencies using vulnerable packages. Without an SBOM, you lack visibility into the full dependency tree.