DigiCert Software Trust Manager vs SignPath Foundation
DigiCert Software Trust Manager
digicert.comSignPath Foundation
signpath.orgSide by side
| Figure | DigiCert Software Trust Manager | SignPath Foundation |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Code Signing Software | 8.3 (#5) | 7.3 (#20) |
| Headquarters | Lehi, Utah, USA | Vienna, Austria |
| Key protection | Keys can be stored in FIPS 140-2 Level 3 or Common Criteria EAL4+ HSMs, with regional key storage options. | SignPath says certificate private keys are securely generated and stored on a hardware security module. |
| Purpose | Software Trust Manager protects software supply chain integrity through code signing, policy enforcement, and controls over key usage and access. | SignPath Foundation provides code-signing certificates to open-source projects to link published binaries to their repositories. |
Plans
DigiCert Software Trust Manager
- Software Trust ManagerPriced on request
In their own words
DigiCert Software Trust Manager
DigiCert Software Trust Manager governs and automates software signing across artifacts, tools, and teams. Signing workflows can run after security checks and cover containers, binaries, and other artifacts, including Windows packages, Java archives, Android APK/AAB files, and macOS application and installer formats. Teams can use Signing Manager Controller, command-line tools, or the Click-to-sign graphical application, and connect workflows through native connectors, GitHub Actions, CLI tools, and APIs. Role- and team-based access, policy templates, workflows, and approvals govern high-risk signing actions. Logs link signed items to an actor and time for audits and incident response. Keys can be stored in FIPS 140-2 Level 3 or Common Criteria EAL4+ HSMs, with regional storage options. Threat detection includes software composition analysis, static binary analysis, Apple notarization scans, and DAST. Use requires a DigiCert ONE host environment, API key, client authentication certificate, and certificate password; two-factor authentication is required for all users. Pricing is on request, and a 30-day trial is listed.
SignPath Foundation
SignPath Foundation provides code-signing certificates to eligible open-source projects, with signing carried out through SignPath.io. For each release, SignPath.io checks that signed files are automated builds from the project’s stated source repository. Certificate private keys are generated and stored on a hardware security module. Each signing request requires a team member’s approval, and every release requires manual approval. Projects must assign author, reviewer, and approver responsibilities, while all team members must use multi-factor authentication for SignPath and repository access. Eligibility requires an actively maintained project with an existing release, an OSI-approved open-source license, and no proprietary code or malware. Supported build systems include Jenkins, GitHub, GitLab, Azure DevOps, TeamCity, and AppVeyor. Supported targets span Windows executables and scripts, MSI, CAB, AppX/MSIX, NuGet, Java archives, Android packages, RPM and Debian packages, Office macros, XML, JSON, OCI container images, ClickOnce, and other files. The free plan is free for eligible projects. Its certificate identifies SignPath Foundation as publisher, and the Foundation may decline applications.