Skip to content

F20.3 — Source and secret scanning

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

Stories: 3 Closed

Story State Depends on
S20.3.1 — Source scan with Django rules Closed —
S20.3.2 — Secret scan over full history Closed —
S20.3.3 — Enable push protection Closed —

Catch insecure code patterns and committed secrets. CI runs a security linter with Django rules over first-party source, gitleaks scans the full git history, and GitHub push protection is on for the repository.

Design

Decided in ADR-0015: the source scan is ruff's S rules and both scans fail CI. The current commands are in the development guide.

S20.3.1 — Source scan with Django rules

State: Closed

Acceptance: CI runs the scanner over packages/ with Django rules, and a seeded insecure pattern is flagged as F20.1 decides (fail or report).

S20.3.2 — Secret scan over full history

State: Closed

Acceptance: CI runs gitleaks over the full git history, not only the change, and a seeded secret is caught.

S20.3.3 — Enable push protection

State: Closed

Acceptance: GitHub secret scanning and its push protection are enabled on the repository (the owner enabled both on 2026-10-28).

Acceptance

  • S20.3.1: the source scan step runs in CI.
  • S20.3.2: the gitleaks step runs with full history (fetch-depth: 0).
  • S20.3.3: gh api repos/rn-forge/pykit --jq '.security_and_analysis | .secret_scanning.status, .secret_scanning_push_protection.status' prints enabled twice.