← KALYPSO

Code signing policy

How KALYPSO's releases are built and signed, who approves them, and what the app sends over the network.

Windows releases: free code signing provided by SignPath.io, certificate by SignPath Foundation (application in review).

What gets signed

Only KALYPSO's own release files, built from the source code in github.com/kalyppso/kalypso: the Windows installers (.exe and .msi) and the application inside them. Every release is built by the project's release workflow on GitHub-hosted runners, from a tagged commit on main. Nothing is signed from a developer's machine.

KALYPSO is open source under the MIT License. Third-party libraries in the installers are open source and are not signed with the project's certificate.

Team and roles

RoleWhoWhat they do
Committers@chxmxiiMay merge changes to main.
Reviewers@chxmxiiReview every change from someone who is not a committer before it is merged, including changes to build scripts and CI.
Approvers@chxmxiiApprove each signing request by hand, after checking it comes from a release build.

Everyone with access to the repository or to the signing service uses two-factor authentication.

Privacy

KALYPSO has no account, no analytics and no telemetry. It sends nothing over the network unless you ask it to, with one exception: the update check.

These services have their own privacy policies: GitHub, and the model provider you use.

Uninstalling

Windows: Settings, Apps, KALYPSO, Uninstall. macOS: move KALYPSO to the Trash. Linux: remove the AppImage, or sudo apt remove kalypso for the .deb.