Menu
Dependency-Track Screenshot

Improve the Security of your Software Development Process, designed for Small and Medium Businesses

SBOM Tree Image

What is a Software Bill of Materials (SBOM)?

An SBOM is a comprehensive inventory that lists all the software components, libraries, and dependencies used in an application or system. It includes details like component names, versions, suppliers, licensing information, and relationships between components. Think of it as an "ingredient list" for software that provides complete transparency into what's actually running in your applications.

Why SBOMs are Critical for Companies

Regulatory Compliance: Government mandates like the US Executive Order on Cybersecurity now require SBOMs for federal software procurement. Many industries are moving toward similar requirements, making SBOMs essential for maintaining business relationships and avoiding regulatory penalties.

Rapid Vulnerability Response: When a new security vulnerability is discovered, SBOMs allow you to instantly identify which applications and systems are affected. This dramatically reduces the time from vulnerability disclosure to remediation, minimizing your exposure window.

Supply Chain Risk Management: SBOMs help you understand exactly what third-party code you're depending on, enabling better vendor risk assessments and helping you avoid components from untrusted or compromised sources.

License Compliance and Legal Protection: Track all open-source licenses across your software portfolio to avoid costly legal disputes, ensure you're meeting license obligations, and make informed decisions about component usage based on license compatibility.

Customer Trust and Transparency: Many enterprise customers now require SBOMs as part of their vendor security assessments. Providing accurate SBOMs demonstrates security maturity and can be a competitive advantage in sales processes.

Incident Response and Forensics: During security incidents, SBOMs provide crucial information for understanding attack vectors, assessing damage scope, and implementing containment measures quickly and effectively.

Why Dependency-Track?

  • Hosted by us so that your team can focus on building and delivering great software.
  • Unlimited Users and Projects
  • Open-Source by OWASP. No vendor lock-in.
  • Affordable for businesses of all sizes. Subscriptions starting at USD $175/month.
  • CI/CD Integration
  • Self-service and on-demand vulnerability reporting.
  • Automatic and continuous updates with industry-trusted vulnerability feeds (NIST National Vulnerability Database (NVD), GitHub Advisories, Google OSV Advisories, with others coming soon.

Supported Languages

Microsoft.NET  JavaScript  Java  Python  Go  Ruby  PHP  Swift  Objective-C  C  C++  Rust  Scala  Erlang  Nim
Dependency-Track supports these languages and any other sources that a CycloneDX file can be built for. See the full list of CycloneDX generation libraries at cyclonedx.org

How it Works

Manual Mode

Manual Mode

  • Build the CycloneDX file locally
  • Upload the CycloneDX file to Dependency-Track web interface or via the API
  • Review the report in the web interface or via the API
CI/CD Mode

CI/CD Integration Mode

  • Build CycloneDX file locally or trigger a repo pull via the API. Integrations are available for Jenkins, GitHub and GitLab. (If a repo pull is triggered, VioletBeacon will build the CycloneDX file itself.)
  • Dependency-Track analyses the dependencies
  • Results are available via the API and builds are blocked if vulnerabilities are detected. The pass-failure criteria and actions are configurable.
Repo Push Mode

Repo Push Mode

  • VioletBeacon monitors repositories and pulls changes when a change is detected.
  • VioletBeacon analyses the project and builds the CycloneDX file
  • CycloneDX file is pushed to Dependency-Track
  • Results are available via the API or web interface
Standards Mappings

Standards Mappings

VioletBeacon and Dependency-Track can help your organization meet the following information security standards (as applicable to your adopted standards, policies and procedures):