Repository navigation
Commit be8c6e5
committed
docs(security): address GTR review — rolling supported-versions policy, CODEOWNERS, SCA and CI links
Review feedback on the GTR questionnaire flagged two factual errors and a set
of unresolved markers that the repository can in fact answer.
The supported-versions table in SECURITY.md pinned concrete version numbers
and had drifted five minor releases behind the latest release. Restate it as a
rolling policy relative to the latest release so it cannot go stale, and cite
the Releases page as the authoritative list instead of repeating numbers in
prose.
The contributor-ladder answer referenced a top-level OWNERS file, which the
project does not have; promotions go through .github/CODEOWNERS for the
area-scoped Reviewer role and MAINTAINERS.md for the Maintainer roster.
Close the markers that repository evidence settles: e2e and CI workflow links,
the Renovate configuration, the organization-wide Trivy CVE-scanning pipeline
and its triage SLAs, and the real state of artifact signing, SBOM and SLSA
provenance. Replace the vague item count in the draft banner with the seven
substantive gaps that genuinely need measurement or a maintainer decision.
Assisted-By: Claude <[email protected]>
Signed-off-by: Timur Tukaev <[email protected]>1 parent 2c22ebc commit be8c6e5
2 files changed
Lines changed: 30 additions & 23 deletions
0 commit comments