Repository navigation
docs: the code signing policy no longer waits on SignPath Foundation - #86
Merged
Merged
Conversation
SignPath Foundation turned the application down on 2026-10-01 for lack of public signals. The policy page now says only that there is no certificate yet; the spec records the refusal next to the other certificate options.
httpsphl
enabled auto-merge
October 1, 2026 11:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SignPath Foundation turned down Botloft's application on 2026-10-01: the Foundation program needs public signals (stars, forks, contributors, outside references) that the project does not have yet. They welcome a new application later.
docs/code-signing-policy.md: drops the paragraph saying Botloft applied and might be signed by SignPath Foundation; it now says there is no certificate yet and that the page will name the holder when there is one.docs/spec.md(15.5): records the refusal next to the other certificate options.The "Code signing policy" links in the README and release notes (#68) stay.
Docs only, nothing to test against the real Claude Code.