Cybersecurity & Bastion

Dependency-Track

Dependency-Track on a VPS: track the vulnerable dependencies in your applications from their SBOMs, on your own server.

In validation

About Dependency-Track

OWASP Dependency-Track is the open-source software supply chain analysis platform (Apache-2.0 licence). On every build, your CI sends it the application's SBOM — the inventory of its components in CycloneDX format, produced by cdxgen, Syft or the CycloneDX plugin for your build tool. Dependency-Track matches each component against public vulnerability databases (NVD, GitHub Advisories, OSV), scores it, and warns you when a vulnerability affects a version you run in production — even months after deployment, without rerunning a build. Policies block a forbidden licence or an outdated dependency. Installed on your VPS, the inventory of your applications stays with you.

What gets installed

Ready when the VPS starts

Compatible OS
Choice of Linux distributions
Application
Dependency-Track
Tech stack
DockerJavaPostgreSQLnginx
Minimum RAM
4 GB minimum
Minimum CPU
2 vCPU
Default port
8127
Access
root over SSH

Key features

  • Continuous inventory: every CycloneDX SBOM sent by your CI updates the list of the application's components and their versions.
  • Known vulnerabilities matched automatically against public databases (NVD, GitHub Advisories, OSV), with their severity and exploitability score.
  • Retroactive alerts: a vulnerability published after deployment is flagged on the versions already in production, with no new build.
  • Security, licence and operational policies: reject a licence, a severity or a component, and see it as soon as the SBOM is uploaded.
  • Notifications to Slack, Microsoft Teams, a webhook or email, filtered by project and severity level.
  • A complete REST API and per-team API keys: upload SBOMs from GitHub Actions, GitLab CI or Jenkins, and export the results.

When to use this solution?

Know in a minute who is affected by a vulnerability

A critical vulnerability is published in a widely used library: a search on the component lists the projects and versions that ship it.

Fail a build on a vulnerable dependency

The pipeline uploads the SBOM, waits for the analysis and reads the policy violations; above the threshold you set, the release waits for the upgrade.

Answer a client audit or a tender

SBOMs and the history of handled vulnerabilities are presented by project and by version, in the CycloneDX format that clients and auditors know how to read.

Guide

Deploy Dependency-Track on your VPS

  1. Create the VPS and choose the address

    Order an Ubuntu 24.04 VPS with at least 4 GB of RAM and 2 vCPUs. Dependency-Track requires a domain: your pipelines upload their SBOMs to it over HTTPS, and the interface opens there. It installs on a subdomain of one of your domains, or on the VPS's free subdomain (dependency-track.{dns_slug}.servorbit-dns.com), HTTPS included. No need to buy a domain name.

  2. Install Dependency-Track from the Marketplace

    In your client area, select Dependency-Track, choose the address and click Install. The script deploys the official images (API server, web interface) with PostgreSQL and an internal proxy that serves the interface and the API on the same address, replaces the admin account's factory password with a generated one and configures the nginx reverse proxy over HTTPS. The first start takes one to three minutes; the vulnerability databases then keep downloading in the background.

  3. Log in for the first time

    Open https://your-domain and log in with the user admin and the password shown in your client area. The factory password admin/admin no longer works. Then create your team's accounts under Administration, Access Management.

  4. Create an API key for your CI

    In Administration, Access Management, Teams, open the Automation team and generate an API key. It carries the permission to upload SBOMs; store it in your CI secrets, never in the repository.

  5. Upload a first SBOM

    Generate your application's SBOM, for example with cdxgen or Syft, then send it to the API from your CI: curl -X POST https://your-domain/api/v1/bom -H "X-Api-Key: $DT_API_KEY" -F autoCreate=true -F projectName=my-app -F projectVersion=1.0.0 -F [email protected]. The project appears in the portfolio and its vulnerabilities show up once the analysis is done.

Proof

What we promise, and how to check it

  • The recommended size, for every application

    The memory required and the VPS that covers it, on every card.

    Check it: the “Recommended VPS” line of each card

  • Root access, on your server

    You administer the system over SSH; your data stays on your VPS.

    Check it: the “What is installed” section of each page

  • You pay for the VPS, not the software

    The applications are open source: your only cost is the VPS that runs them.

    Check it: in the cart, no line for the application

Frequently asked questions

Questions about Dependency-Track

← Back to Cybersecurity & BastionAll applications
A scanner inspects an image or a repository at the moment you run it. Dependency-Track keeps the inventory of all your applications and their versions, and re-evaluates it continuously: a vulnerability published next week will be flagged on what you deploy today. The two complement each other — a scanner can in fact produce the SBOM you send to Dependency-Track.

Activate Dependency-Track on your infrastructure.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.

All applications

Dependency-Track also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers