Skip to content

F20.5 — Disclosure and posture

State Closed
Parent E20
Iteration Release 7
Start Date 2026-10-28
Closed Date 2026-10-30
Predecessors F20.1
Source Owner request, 2026-10-26

Stories: 4 Closed

Story State Depends on
S20.5.1 — SECURITY.md Closed —
S20.5.2 — OpenSSF Scorecard Closed —
S20.5.3 — Per-release evidence page Closed —
S20.5.4 — Enable private vulnerability reporting Closed —

Say how to report a vulnerability and show the baseline's state. The repository gets a SECURITY.md, OpenSSF Scorecard runs in CI, and each release gets an evidence page listing the baseline results.

Design

Decided in ADR-0015: the evidence page sits beside its release, at docs/releases/release-<n>/; the reporting channel is GitHub private vulnerability reporting; Scorecard reports and sets no threshold. The current controls are in the development guide.

S20.5.1 — SECURITY.md

State: Closed

Acceptance: SECURITY.md at the repository root gives the reporting channel and the supported versions.

S20.5.2 — OpenSSF Scorecard

State: Closed

Acceptance: a Scorecard run is part of CI and its result is recorded.

Evidence: the Scorecard run succeeded on ed566a0, and the published score is 7.2 (Scorecard v5.6.0).

S20.5.3 — Per-release evidence page

State: Closed

Acceptance: each release has a page listing the result of every baseline control, and the release runbook says to fill it at the cut.

S20.5.4 — Enable private vulnerability reporting

State: Closed

The owner turns it on under the repository's Security settings, so SECURITY.md's reporting link accepts reports. Enabled 2026-10-28.

Acceptance: gh api repos/rn-forge/pykit/private-vulnerability-reporting returns {"enabled":true}.

Acceptance

  • S20.5.1: SECURITY.md exists with both sections.
  • S20.5.2: the Scorecard workflow runs.
  • S20.5.3: the docs build passes with the evidence page.
  • S20.5.4: private vulnerability reporting is enabled.