Codenotary Trustcenter vs OWASP Dependency-Track

Codenotary Trustcenter manages software bills of materials (SBOMs) and applies trust enforcement to applications and their components. It can import and export SBOMs in any format, create detailed SBOMs for open-source applications or containers, and analyze them. The platform tracks component provenance and trust levels, flags unknown or untrusted components, and monitors attestations and application and stack risk profiles. It provides real-time application risk scores with reachability analysis and can enforce deployment of container images built with known, trusted components. Trustcenter also supports software risk profiles for compliance and audit work, plus artifact attestation guidance such as in-toto. Listed integrations include CI/CD and SCM tools, Docker and OCI registries, Snyk, Aqua, JFrog, Jenkins, GitLab, GitHub, Kubernetes, and AWS Lambda. Language bindings include Java, C++, Python, Node.js, Go, Rust, and PHP. Trustcenter/Teams is offered on-premises or in the cloud, with component discovery, dependency tracking, centralized SBOM storage, and continuous vulnerability scanning. Enterprise plans start at $3,600 a month; Teams pricing is by quote. A 30-day trial is listed.

OWASP Dependency-Track is a free, self-hosted platform for managing software-component risk across a supply chain. It builds inventories from software bills of materials and identifies vulnerable components, supporting CycloneDX SBOM, HBOM, VEX, and VDR documents for ingestion, analysis, and production. Components can be matched against NVD, GitHub Advisories, OSV, OSS Index, Snyk, Trivy, and VulnDB, while integrated EPSS support helps prioritize mitigation. Integrity checks flag components when published hashes differ from those served by an upstream registry. A Common Expression Language policy engine evaluates component rules and can break a build when a policy fails. Alerts can be filtered by event fields and sent to Slack, Teams, Mattermost, email, or webhooks. API and web interfaces are available, with least-privilege portfolio access and single sign-on through OpenID Connect, Active Directory, and LDAP. Version 5.1 uses separate API and frontend container images, supports Kubernetes, and requires PostgreSQL.