Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
An OWASP component-analysis platform for the software supply chain: your build pipeline uploads a Software Bill of Materials for each project, and Dependency-Track tracks those components against vulnerability data, applies component policies and routes notifications to Slack, email or a webhook, with a REST API for automation. Version 5 runs an API server, a separate web frontend and PostgreSQL; the API server container is limited to 2 GB in the project's own Compose file. Apache-2.0. It watches the dependencies you ship rather than scanning hosts or networks.
Runs on a VPS from $24/mo (Kamatera 8GB, 8 GB RAM) · prices checked Nov 2026
Fits home hardware (483 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Dependency-Track when the question is which of the libraries inside your own software have known vulnerabilities, across many projects at once and over time. Your build pipeline uploads a Software Bill of Materials (SBOM) for each project, and the platform tracks those components continuously, applies component policies and sends notifications to Slack, email or a webhook; it also has a REST API. It is an OWASP project under Apache-2.0. Our snippet is the project's quickstart Compose file: API server, web frontend and PostgreSQL, with images pinned to 5.2.1 (released 2026-10-25), a generated database password, and the API server limited to 2 GB as upstream ships it. The v5 production guide starts the API server at 2 GB and says PostgreSQL should not go below 4 GB even for evaluation, which is the source of our 4096 MB floor. The other Security entries do different jobs: 2FAuth stores one-time-password codes, CrowdSec bans abusive IPs found in server logs, and step-ca issues certificates. Dependency-Track is the only one that analyses the components in software you build.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Dependency-Track — software composition analysis — based on the project's quickstart Compose file, pinned to 5.2.1 (released 2026-10-25)
echo "POSTGRES_PASSWORD=$(openssl rand -hex 16)" > .env
cat > docker-compose.yml <<'EOF'
name: dependency-track
services:
apiserver:
image: ghcr.io/dependencytrack/apiserver:5.2.1
depends_on:
postgres:
condition: service_healthy
deploy:
resources:
limits:
memory: 2g
environment:
DT_DATASOURCE_URL: "jdbc:postgresql://postgres:5432/dtrack"
DT_DATASOURCE_USERNAME: "dtrack"
DT_DATASOURCE_PASSWORD: ${POSTGRES_PASSWORD}
ports:
- "127.0.0.1:8080:8080"
volumes:
- "apiserver-data:/data"
restart: unless-stopped
frontend:
image: ghcr.io/dependencytrack/frontend:5.2.1
environment:
API_BASE_URL: "http://localhost:8080"
ports:
- "127.0.0.1:8081:8080"
restart: unless-stopped
postgres:
image: postgres:18-alpine
environment:
POSTGRES_DB: "dtrack"
POSTGRES_USER: "dtrack"
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
healthcheck:
test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
interval: 5s
timeout: 3s
retries: 3
volumes:
- "postgres-data:/var/lib/postgresql"
restart: unless-stopped
volumes:
apiserver-data: {}
postgres-data: {}
EOF
docker compose up -d
timeout 600 bash -c 'until curl -fsS -o /dev/null http://localhost:8080/api/version; do sleep 5; done'
# → http://localhost:8081 on the server itself (ports bind to 127.0.0.1 as upstream ships them; reach it with ssh -L 8081:localhost:8081 -L 8080:localhost:8080 — log in as admin / admin; it asks you to change the password at first login)Dependency-Track's quickstart and README flag these before you rely on it:
Dependency-Track used 483 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 4096 MB.
The Dependency-Track install snippet is marked verified on Ubuntu 26.04 (Nov 2026).