Code signing policy
Promptline's Windows releases are code-signed from 0.2.28.
They are signed with a Certum Open Source Code Signing certificate, issued to the maintainer after Certum checked the maintainer's identity. This page is the policy those releases follow: what is signed, who signs it, and what the app sends over the network.
Status. 0.2.28 is the first signed release; everything before it is unsigned. The certificate runs until 5 November 2027.
What is signed
Every Windows release carries two installers built from this repository's source: Promptline_X.Y.Z_x64-setup.exe (NSIS) and Promptline_X.Y.Z_x64_en-US.msi. The app itself, promptline.exe, is signed before it is packed into each installer, and then each installer is signed, so the download and the program it installs carry the same signature. The NSIS installer's uninstaller and plug-ins are signed too. Each signature carries a timestamp from Certum, so it stays valid after the certificate expires.
Windows names the publisher as Open Source Developer Alpaslan Bek. The certificate's private key stays in Certum's cloud service, SimplySign; it never sits on a disk or in the repository, and using it takes a login with a one-time code from the maintainer's phone. Signing doesn't end every warning at once: SmartScreen can still warn about a new release until it has built a reputation.
Separately, each installer carries an updater signature made with the maintainer's own key, which stays on the maintainer's machine and never goes to GitHub. An installed copy of Promptline installs an update only if that signature matches the key built into it and names the version on offer.
How a release is signed
- The maintainer tests
master, where CI has passed, and logs in to SimplySign. - The maintainer builds the release on a personal machine. The build signs the program, then the installers, then adds the updater signature over the signed installers.
- The maintainer checks the signatures and publishes the release on GitHub.
Nothing is signed without the maintainer logged in. CI builds stay unsigned, so a pull request can't reach the key.
Team roles
Promptline has one maintainer, who holds every role.
- Committers and reviewers
- Alpaslan Bek (@bekalpaslan) writes and reviews every change. Outside contributions arrive as pull requests and are merged only after that review.
- Signing
- Alpaslan Bek (@bekalpaslan) builds and signs each release.
Team members must use multi-factor authentication on GitHub and on SimplySign.
Privacy
No telemetry. One update check, off in a click. At startup and once a day Promptline fetches one small file, https://promptline.cc/latest.json, to see whether a newer release exists. The address is fixed and the same for everyone; the request carries nothing about you (no version, no ID, no usage). Like any web request it reaches GitHub Pages, which hosts promptline.cc and logs IP addresses, and it names the updater library as its user agent. If you accept an update, the installer downloads from GitHub Releases and is installed only if its signature matches the key built into the app. Turn the check off under Settings → About; Check for updates there still works by hand. Nothing else leaves your machine except what you paste.
Promptline collects no user data and transfers none to other systems. The update check sends nothing about you, so the installer has no privacy page or opt-out of its own; Settings → About turns the check off. Your prompts, packs and settings are files on your own machine, and so is the log (promptline.log), which leaves it only if you attach it to a bug report.
This site's own privacy note is at the foot of the home page.
Questions and reports
Report a security problem through GitHub's private vulnerability reporting or to security@promptline.cc (SECURITY.md). Anything else goes to the issue tracker.