Double Open Compliance vs SourceTrust

Double Open Compliance automates software security and license compliance with deterministic filters and framework-anchored AI agents. It addresses legal due diligence for the EU Cyber Resilience Act, NIS2, and DORA. ORT Analyzer captures transitive dependencies according to how software is built, while Double Open Server provides global file-level caching that the site says enables 10x faster scanning. The platform produces machine-readable SBOMs in CycloneDX and SPDX formats and manages GitHub, GitLab, and air-gapped projects. AI agents surface ambiguous exceptions for human verification or version-controlled pull requests. Vulnerability triage ranks CVEs by code reachability and package roles and proposes evidence-backed resolutions. Deployment can be SaaS or customer-hosted, with data in EU-controlled datacenters or on customer infrastructure. The ORT stack includes a web UI, dashboards, REST API, and identity management.

SourceTrust helps teams review third-party software licenses and publish shareable compliance pages for shipped products. It collects direct and transitive dependencies from repositories, lockfiles, and SBOMs into one inventory. The service retrieves each shipped package, compares it with the registry digest, and reads the license text inside. Nothing is published until a team reviews and confirms the record, while packages needing a decision are flagged. Connections include GitHub, GitLab, and Azure DevOps, with lockfile and SBOM imports across 14 formats and 9 ecosystems. Outputs include a hosted attestation page, THIRD_PARTY_LICENSES.md, NOTICE, CycloneDX, SPDX, JSON, CSV, plist, and branded PDF. Repository synchronization and publish-drift checks identify changes from the published snapshot. Pages can be password-protected or excluded from search engines. Eligible public GitHub projects can publish for $0 under fair use and attribution. Yearly project billing is $299.00 per year.