Software composition analysis: know what your applications are made of
Every application is built from open source, third-party and in-house components. SMART TS XL scans your existing code base, builds an accurate bill of materials and shows the license and security risks hidden in it, several layers deep.
What is software composition analysis?
Software composition analysis (SCA) identifies the open source components in a codebase and gives teams more visibility. Organizations use it to build an inventory of all code components, open source, proprietary and third-party commercial, and then evaluate and manage code quality, security and license compliance.
Without SCA, tracking these components by hand is an arduous task that often leads to overlooked code and the vulnerabilities that come with it.
Undiscovered open source components can carry license compliance issues that affect your reputation, IP and bottom line, and vulnerabilities that attackers will exploit. SMART TS XL is a software composition analysis engine that scans your existing code base and breaks down the interconnected systems behind your applications.
無し SMART TS XL
- No single list of what each application contains
- Transitive dependencies invisible
- Licenses discovered during an audit
- Vulnerable versions found after an incident
自律的AI SMART TS XL
- An accurate bill of materials for every application
- Dependencies assessed several layers deep
- Unknown and risky licenses flagged for review
- Outdated and vulnerable versions surfaced early
Benefits of software composition analysis
Recognize CVEs
Recognize Common Vulnerabilities and Exposures in the components you use.
Expose hidden threats
Use transitive dependencies to show threats hidden several layers down.
License and IP compliance
Identify open source licensing and IP compliance risks, including unknown licenses.
部品表
Create an accurate bill of materials (BOM) for all applications.
Metrics for decisions
Generate metrics that drive better decisions and prioritize the applications most critical to the business.
継続的な可視性
Flexible scans and fast feedback across the software development life cycle.
認定条件 SMART TS XL builds the bill of materials
スキャン
Scan the existing code base and its build and dependency files.
Java · .NET · JS棚卸
List every open source, third-party and proprietary component.
214つのコンポーネント分析
Check versions, licenses and known vulnerabilities, layers deep.
3 CVEs · 2 reviews優先順位をつける
Rank findings by risk and by how critical the application is.
Fix first: log4j-coreComposition Analysis, in plain English
Everything on this page also works as a question. Ask ASK AI inside SMART TS XL, or the assistant your team already uses through the MCP Connector. It calls SMART TS XL, reads the indexed code and answers with the source behind every fact. Read-only, under the same permissions your people have.
Build a bill of materials for our Java applications.
12 Java applications use 1,906 components: 1,214 open source, 83 third-party and 609 in-house. claims-web has the most, with 214.
- 12アプリ
- 1,906つのコンポーネント
- BOM ready
ILLUSTRATIVE QUESTIONS AND RESULTS
What SCA gives your team
Gain complete visibility
Complete visibility into the open source in your entire code base, so your team can find the code and make changes when needed.
Automatically track open source components
It is no longer humanly possible to track every way attackers might bypass the security perimeter. Automated scans keep track of vulnerabilities, dependencies and licenses and report every instance found.
Vulnerability remediation and prioritization
Assess technical risk, effort to fix and size of change for each vulnerability, decide which ones in open source libraries are relevant, and prioritize with confidence.
継続的なセキュリティ監視
Static checks are not enough for code that changes often, or for code that sits unchanged while new exploits appear. Continuous monitoring keeps visibility current and can alert on pre-configured triggers.
Maintain open source license compliance
Flag components with unknown licenses, summarize license obligations in plain terms and help development and legal teams assess the impact of including a component.
What SCA looks for
Open source components, out-of-date library versions, security vulnerabilities, licenses for usage and compliance data, and license expiration dates.
Proven on 5.7 billion lines of code
Questions about composition analysis
Which component types are covered?
Open source, third-party commercial and proprietary components, including dependencies pulled in transitively by other components.
Does SCA replace our security scanner?
それはそれを補完します。 SMART TS XL adds the inventory and the cross-reference of where each component is used, so findings can be traced to the applications and code that depend on them.
どのように始めましょう?
Contact us or book a live demo. We will scan a sample application and walk through its bill of materials with your team.
See composition analysis on your own code.
In a live session we load a sample of your portfolio and run composition analysis in the web interface and through the AI assistant you already use.
への新しい SMART TS XL? See how the platform fits together →
