DocsGetting Started

OSSign Documentation

OSSign provides free code signing for qualifying open source projects. Your releases are built and signed with OSSign's* trusted certificates through a public, verifiable CI pipeline, and your repository never holds a signing secret.

Who These Docs Are For

Maintainers of projects that have been accepted into OSSign. Start with How It Works, then set up your signing workflow and request your first signed build.

Projects thinking about applying. Read the Project Rules first, then head to ossign.org for the current application status.

Questions?

Reach out through your application ticket, or use the contact form on ossign.org. You can also reach us on our Matrix server at #general:matrix.ossign.org.

Certificates

The trusted certificates OSSign uses to sign your releases are publicly verifiable, and generally include OSSign as part of the name along with one of the companies that sponsors us with the use of the certificates.

We are not able to provide project-specific certificates, certificates with other or custom names, certificates for private use, any certificates at all really. We only provide signing as a service.

If you want a project-specific certificate, you can apply for one through the SignPath foundation, you can get one from Certum, or you can apply for access to Azure Artifact Signing as an individual or organization.

Edit This Page on GitHub Maintained by the OSSign team, Uppsala, Sweden