Skip to content

docs: align security response times - #199

Merged
KyleJune merged 1 commit into
mainfrom
docs/align-security-response-times
Nov 12, 2026
Merged

KyleJune merged 1 commit into
mainfrom
docs/align-security-response-times

Conversation

@KyleJune

Copy link
Copy Markdown
Member

What changed

SECURITY.md response commitments:

  • Acknowledgment: 72 hours → 5 business days
  • Substantive assessment: 7 days → 14 days

The 90-day disclosure window, the no-bounty statement, the contact address and everything else are unchanged. llms-full.txt is regenerated from SECURITY.md with pnpm llms:generate (the only lines that changed in it are the same two sentences). No other file in the repo (README, docs/) repeats these times.

Why

The old times were tighter than the maintainer can reliably keep as a solo maintainer. These are promises the project can keep: a 5-business-day acknowledgment and a 14-day substantive assessment, with the 90-day disclosure window still in place.

Verified

  • pnpm check from the repo root passes (build, examples typecheck, oxlint, oxfmt, tsc, doc-lint, doc-check, doc-links, llms:check).
  • grep for 72 hours, 7 days, and acknowledgment wording across the repo finds only SECURITY.md and its generated copy in llms-full.txt. docs/triage.md states a separate 3-business-day issue-triage target for public issues; it is not the security commitment and is unchanged.

🤖 Generated with Claude Code

SECURITY.md promised an acknowledgment within 72 hours and a substantive
assessment within 7 days. Change the commitments to 5 business days and
14 days, the times the maintainer can keep. The 90-day disclosure window
is unchanged. llms-full.txt is regenerated from SECURITY.md.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@KyleJune
KyleJune merged commit 9e74a2e into main Nov 12, 2026
10 checks passed
@codecov

codecov Bot commented Nov 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.07%. Comparing base (4d208f4) to head (3c34167).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #199   +/-   ##
=======================================
  Coverage   94.07%   94.07%           
=======================================
  Files         148      148           
  Lines       11729    11729           
  Branches     2765     2765           
=======================================
  Hits        11034    11034           
  Misses        232      232           
  Partials      463      463           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.54.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant