docs(security): add SECURITY.md security policy#473
Merged
Conversation
Repo security policy: supported-version window, private vulnerability reporting (GitHub advisories preferred, email fallback), triage and coordinated-disclosure expectations, and a StitchAPI-specific scope (credential leakage, OpenAPI codegen injection, playground sandbox escape). Clears a v1.0 GA-cut checklist item. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Acknowledge within 48h (was 3 business days) and frame fixes by severity rather than a 90-day figure that read as "we'll take 3 months". Reword the out-of-scope application-code item to describe root cause instead of "your own ... merely uses". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
Adds a repository security policy at the repo root (
SECURITY.md), where GitHub's Security tab and the new-issue flow surface it. The repo previously shipped without one, so GitHub's community-standards check flagged it missing and vulnerability reporters had no documented private channel.Contents
1.0.x/1.0.0-rc.xreceive security fixes;0.xdoes not.Why
Clears one of the v1.0 GA-cut checklist items (see
docs/RELEASE.mdand the GA blockers).Notes
🤖 Generated with Claude Code