Skip to content

Commit 9cc8c6c

Browse files
committed
docs(security): make the disclosure line and the support test checkable
A second internal pass found that the previous commit's disclosure argument did not hold together and that its support test could not be evaluated by a reader. The document had nominated the monthly aggregate summaries as safe-to-publish evidence on the grounds that they hold no vulnerability detail. They do: they name accepted-risk findings individually by CVE ID, severity and package, some of them critical, next to a count of confirmed findings awaiting a fix. State the line where it actually falls — aggregate counts by severity are publishable, naming an individual unfixed finding is not, because a CVE ID plus a package plus this project's public pinned component list locates unpatched exposure — and note that the monthly summary needs reducing to counts before it can be published. Present the resulting posture as a proposal rather than as a position the maintainers have taken. The scanner SLA paragraph said a triage backlog was running against the clock. The pipeline's own output says something more specific and worse: triage is keeping up, remediation is not, with the last monthly period closing on no confirmed findings fixed. Say that instead. The supported-versions table keyed support to having an active release branch. Release branches are never deleted, so every line back to the earliest has one and the test tells a reader nothing; read literally it also committed the project to every 1.x line. Key it to patch activity within a stated window instead, restore an end-of-life category the previous commit had removed entirely, and put the v0.41 cutoff back rather than extending discretionary backports across all of 0.x. Also: drop an unevidenced claim that the per-PR checks are healthy, correct the nightly attribution — the current red run is a regression after #3332 and is not tracked by an issue, unlike the older failure in #3278 — and qualify how zizmor gates, through the required pre-commit hook rather than through its own path-filtered workflow. Assisted-by: LLM Signed-off-by: Timur Tukaev <[email protected]>
1 parent a134e13 commit 9cc8c6c

2 files changed

Lines changed: 18 additions & 14 deletions

File tree

0 commit comments

Comments
 (0)