ИИ-платформа для связи с клиентами
Веб-виджет, Telegram, Макс, VK, Email - в одном чате. Поддержка MCP, RAG, BYOK, веб-звонки и голосовые с расшифровкой
Chatballs
Попробовать бесплатно

Code signing policy

Last updated: November 13, 2026

This policy describes Windows code signing for MarkMello, maintained by Andrey Ermolaev (dartdavros).

Free code signing provided by SignPath.io, certificate by SignPath Foundation.

Current signing status

Test signing has been verified for the MarkMello application and installer on Windows x64 and ARM64. The GitHub Actions test run records the successful integration checks.

Production certificate provisioning is still pending. The release-signing policy cannot be used until its production certificate is active. Test certificates are not trusted production certificates and are not used to represent public releases as trusted Windows software.

Existing unsigned downloads remain unsigned. A release will be described as signed only after production signing and signature verification have succeeded.

Team and responsibilities

What is signed

The Windows signing workflow builds MarkMello from its public source repository on GitHub-hosted runners. It submits the MarkMello application binaries for signing before packaging, then submits the Windows installer for signing. Signatures are verified before signed release assets are published.

The project certificate is used for MarkMello-owned binaries and installers. Third-party libraries may be included in the package, but their existing signatures are not replaced with MarkMello's signing identity.

Release approval and key protection

Every production signing request requires explicit approval in SignPath. A successful build does not automatically approve a release. Application and installer requests are approved separately, including requests for each supported Windows architecture.

SignPath verifies the origin of submitted build artifacts. The production certificate is issued to SignPath Foundation; its private signing key is held in SignPath's hardware security module and is not distributed with the source repository or application.

The integration and artifact definitions are documented in the project's SignPath setup. The process follows the SignPath Foundation conditions.

Privacy

See the Privacy Policy for website analytics, cookies, local document handling, application update checks, and connections to third-party services.

Questions

Contact the maintainer through the MarkMello repository or GitHub profile with questions about release signatures or this policy.