Signo
github.com
Spec sheet
- Purpose
- Signo is an open source, self-hosted signing service that signs files through an HTTP API.Read 10 Oct 2026 · github.com
- Integrations
- The README names YubiKey as a hardware-token example and points to a separate signo-client NPM package for API use.Read 10 Oct 2026 · github.com
- License
- The repository identifies the project as GPL-3.0 licensed.Read 10 Oct 2026 · github.com
- API access
- API clients, called signees, can be assigned access to individual signing engines, and API requests are HMAC signed.Read 4 Oct 2026 · github.com
- API authentication
- API requests are HMAC signed.Read 10 Oct 2026 · github.com
- Databases
- Configuration supports either MySQL or SQLite.Read 10 Oct 2026 · github.com
- Distribution
- The project says Signo is available through NPM or Docker Hub, with NPM described as the simplest installation route.Read 4 Oct 2026 · github.com
- File signing
- It signs files through an HTTP API and supports plain signatures and Authenticode signing for Windows executables.Read 4 Oct 2026 · github.com
- Installation
- The README offers installation through NPM or Docker Hub and describes a Linux setup requiring Node.js 16 or 18.Read 10 Oct 2026 · github.com
- Intended use
- The project aims to let CI applications generate signed executables using certificates stored on hardware tokens.Read 4 Oct 2026 · github.com
- PKCS#11
- Signo supports PKCS#11 tokens and is intended to help CI applications use hardware-stored code-signing certificates.Read 10 Oct 2026 · github.com
- Planned features
- The README lists a cryptographically verifiable operation log, PDF signing, key and CSR generation, and importing certificates to tokens as planned features.Read 10 Oct 2026 · github.com
- Runtime requirement
- The quick start calls for a Linux machine with NodeJS 16 or 18 installed.Read 4 Oct 2026 · github.com
- Security setup
- The setup instructions require configuring an SSL certificate and listing PKCS#11 modules.Read 4 Oct 2026 · github.com
- Signature types
- It supports plain signing, which returns a binary signature, and Authenticode signing for Windows executables.Read 10 Oct 2026 · github.com
- Signing permissions
- Administrators can enable specific signing engines for each signee, which represents an API client.Read 10 Oct 2026 · github.com
- Token controls
- The service lists detected tokens and their keys and certificates; a token must be activated by entering its PIN before it can sign.Read 10 Oct 2026 · github.com
- Transport security
- The setup instructions require an SSL certificate for the HTTPS service, and say a self-signed certificate can be used if the infrastructure trusts it.Read 10 Oct 2026 · github.com
- User management
- Multiple users can manage tokens, signing engines, and signees.Read 10 Oct 2026 · github.com
Where Specifiction places it
- Code Signing Software#25 of 286.9