Freedom251 › Code Signing Software
SignPath Foundation

What SignPath Foundation is
SignPath Foundation provides code-signing certificates to eligible open-source projects, linking published binaries to their repositories. SignPath.io performs the signing and checks that signed files for each release are automated builds from the project’s stated source repository. Certificate private keys are generated and kept on a hardware security module. Every release requires manual approval, with projects defining author, reviewer, and approver responsibilities and a team member approving each request. Eligible projects must be actively maintained, already released, use an OSI-approved open-source license, and contain no proprietary code or malware. Team members must use multi-factor authentication for SignPath and repository access. Supported trusted build systems include Jenkins, GitHub, GitLab, Azure DevOps, TeamCity, and AppVeyor. The free subscription is for eligible open-source projects. The certificate names SignPath Foundation as the publisher, and the Foundation may accept or reject applications at its discretion.
Who it suits
SignPath Foundation is for actively maintained, released open-source projects that meet its licensing and content requirements. Teams must be prepared to use multi-factor authentication and require manual approval for every signing release.
What it does well
- Certificate private keys are kept on a hardware security module
- Verifies signed files are automated builds from the stated repository
- Supports several trusted build systems
- Free subscription for eligible open-source projects
What to know first
- Every release requires manual signing approval
- Eligibility excludes proprietary code and malware
- Certificate names SignPath Foundation as publisher
- The Foundation may reject an application
Limits
The free subscription is limited to eligible open-source projects that are actively maintained, already released, licensed under an OSI-approved license, and contain no proprietary code or malware. Every release requires manual signing approval.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Free OSS SignPath.io subscription | For eligible open-source projects · project must be actively maintained and released · OSI-approved license · every release requires manual signing approval | Free |
As signpath.org lists them, read 4 Oct 2026. The maker's own page has the final word.
Getting started
- Review the project eligibility requirements on the SignPath Foundation website.
- Apply for the free subscription; acceptance is at the Foundation’s discretion.
- Ensure all project team members use multi-factor authentication for SignPath and repository access.
- Set up a supported trusted build system.
- Define author, reviewer and approver responsibilities, then have a team member approve each signing request.
Verdict
SignPath Foundation offers signing certificates for qualifying open-source projects, with build verification and protected keys. Manual approval is required for each release, and applying does not guarantee acceptance.
Questions
Does SignPath Foundation have a free plan?
Yes. The Free OSS SignPath.io subscription costs 0.00 USD for eligible open-source projects.
What are the eligibility requirements?
A project must be actively maintained, already released, use an OSI-approved open-source license, and contain no proprietary code or malware. The Foundation may accept or reject applications at its discretion.
Which build systems are supported?
The documentation lists Jenkins, GitHub, GitLab, Azure DevOps, TeamCity and AppVeyor as supported trusted build systems.
Does signing happen through SignPath Foundation itself?
SignPath.io performs the code signing. For each release, it verifies that signed files are automated builds from the project’s stated source repository.
What kinds of files can it sign?
Supported targets include 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 arbitrary files.
Who is named as the publisher?
The certificate is issued to SignPath Foundation, so SignPath Foundation is named as the software publisher.
Facts from SignPath Foundation's own pages
- Acceptance discretion
- The Foundation may accept or reject an application at its discretion and is under no obligation to accept a project. · signpath.org, 4 Oct 2026
- Approval requirement
- Every release requires manual approval for signing. · signpath.org, 4 Oct 2026
- Build integrations
- The documentation lists Jenkins, GitHub, GitLab, Azure DevOps, TeamCity, and AppVeyor as supported trusted build systems. · docs.signpath.io, 4 Oct 2026
- Build verification
- For each release, SignPath.io verifies that signed files are automated builds from the project’s stated source repository. · signpath.org, 4 Oct 2026
- Certificate identity
- The Foundation certificate is issued to SignPath Foundation, which is therefore named as the software publisher. · signpath.org, 4 Oct 2026
- Eligibility
- Eligible projects must be actively maintained, already released, use an OSI-approved open-source license, and contain no proprietary code or malware. · signpath.org, 4 Oct 2026
- Headquarters
- Vienna, Austria · signpath.org, 28 Sept 2026
- Key protection
- SignPath says certificate private keys are securely generated and stored on a hardware security module. · signpath.org, 4 Oct 2026
- Operator
- SignPath Foundation says it is currently operated by SignPath GmbH, the company behind SignPath.io. · signpath.org, 4 Oct 2026
- Purpose
- SignPath Foundation provides code-signing certificates to open-source projects to link published binaries to their repositories. · signpath.org, 4 Oct 2026
- Signing roles
- Projects must define author, reviewer, and approver responsibilities, and a team member must approve each signing request. · signpath.org, 4 Oct 2026
- Signing service
- The Foundation provides certificates through SignPath.io, which performs the code signing. · signpath.org, 4 Oct 2026
- Software restrictions
- The Foundation does not sign software with features designed to identify or exploit vulnerabilities or bypass execution-environment security measures. · signpath.org, 4 Oct 2026
- Team security
- All project team members must use multi-factor authentication for SignPath and source-code repository access. · signpath.org, 4 Oct 2026
Where SignPath Foundation stands on Freedom251
- Code Signing Software#10 of 28
