Skip to content

docs: add the code signing policy and name the private reporting channel - #334

Merged
ManuelStaggl merged 1 commit into
mainfrom
docs/code-signing-policy
Nov 11, 2026
Merged

ManuelStaggl merged 1 commit into
mainfrom
docs/code-signing-policy

Conversation

@ManuelStaggl

Copy link
Copy Markdown
Collaborator

Preparation for signing the Windows installer through the SignPath Foundation (the application follows; nothing is signed yet).

  • docs/code-signing-policy.md: what is signed, the team roles, the privacy statement, how to uninstall; with the line the foundation's terms ask for.
  • README: a "Code signing policy" section that links to it.
  • SECURITY.md said the repository was private; it now names GitHub's private vulnerability reporting, which is switched on.

The policy says that only releases from the first signed one on carry a signature.

🤖 Generated with Claude Code

The policy the SignPath Foundation asks for: what is signed, the team
roles, the privacy statement and how to uninstall. SECURITY.md still
said the repository was private.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@ManuelStaggl
ManuelStaggl merged commit 6c87e3b into main Nov 11, 2026
7 checks passed
@ManuelStaggl
ManuelStaggl deleted the docs/code-signing-policy branch November 11, 2026 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant