Skip to content

FOLLOW-UP: Consider binary signing for macOS/Windows releases #130

@adnaan

Description

@adnaan

Context

This follow-up task was identified during the review of PR #122.

Source PR: #122
PR Title: feat: add CLI release workflow and Homebrew support
Suggested by: @claude[bot]

Task Description

Consider adding code signing and attestation for improved supply chain security.

Areas to Consider

  1. macOS code signing: Sign binaries with Apple Developer certificate to avoid Gatekeeper warnings
  2. Windows code signing: Sign with Authenticode certificate for Windows SmartScreen
  3. SLSA provenance: Generate SLSA provenance attestations
  4. GitHub Artifact Attestation: Use GitHub's built-in attestation feature

Prerequisites

  • Apple Developer account (for macOS signing)
  • Code signing certificate (for Windows)
  • Understanding of SLSA and provenance requirements

Priority

This is a nice-to-have for improved security but not blocking for basic functionality.


This issue was automatically created by prmonitor from PR review comments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3-lowLow: extended features, operational docsenhancementNew feature or requestfollow-upFollow-up task from PR reviewfrom-reviewIssue originated from PR review

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions