Code signing policy - Pitboard

What is signed

Files	Signed by
The macOS app and command line	A Developer ID of team `D7HJ5TFYCU`, and notarised by Apple
Windows files Pitboard builds, from the first signed release on	SignPath, with a certificate issued to SignPath Foundation
Windows pre-releases published before that	Not signed
Linux files	Not signed
Files Pitboard did not build	Their own publishers, or not signed

There is no Windows release, so SignPath has signed no Pitboard file. Verify a download checks the macOS signatures. Free code signing provided by SignPath.io, certificate by SignPath Foundation.

Roles

Role	Responsibility	Members
Committers and reviewers	Change the source code without another person’s review, and review every pull request from anyone else before it merges	Ngo Quoc Dat, `datlechin` on GitHub
Approvers	Approve or refuse each signing request	Ngo Quoc Dat, `datlechin` on GitHub

Each member signs in to GitHub and to SignPath with multi-factor authentication.

How a Windows file is signed

The release workflow, release.yml, builds each Windows release on GitHub-hosted runners, from the commit its v* tag names, with no cache. SignPath checks where the files came from, and signs them only after an approver approves the request.

Privacy

Security and privacy is Pitboard’s privacy policy: it lists each request Pitboard makes and what the request carries. What Pitboard sends Anthropic, OpenAI and GitHub also falls under Anthropic’s privacy policy, OpenAI’s privacy policy and GitHub’s privacy statement.