Headline

Risk level: HIGH. Live operational credentials are sitting in committed history of two private repos:

Both repos are private, but rotation is the only true mitigation.

Also today:

Per-repo state

10 repos audited. Detail in Codex log.

Repo Branch Uncommitted Oldest unstaged Last commit
------ -------- ------------: ----------------: -------------
ghost-os main 0 2026-03-23
ha-law main 15 20d 2026-04-16
sail-cases main 2 11d 2026-04-07
sail-hr main 5 27d 2026-04-07
sail-infrastructure agent/projects-reorg-04-18 6 14d 2026-04-23
sail-knowledge agent/living-wiki-refresh-04-24 1 9d 2026-04-24
sail-litify codex/roundtable-qa-04-25 20 34d 2026-04-24
sail-marketing agent/projects-reorg-04-18 7 11d 2026-04-23
sail-seo agent/visual-normalize-04-23 800 12d 2026-04-23
sail-templates agent/trust-strip-04-19 13 27d 2026-04-23

Diverged branches >7 days (active)

The agent/projects-reorg-2026-04-18 branch persists across infrastructure, marketing, and litify. The agent/trust-strip-sitewide-2026-04-19 branch persists across sail-seo and sail-templates. Both are 11–16 days old. Decision needed: merge or abandon.

Secret exposure detail

Secret Repo Files in HEAD Distinct commits
-------- ------ --------------: -----------------:
WordPress App Password sail-knowledge 40 2
WordPress App Password sail-seo 2 2
Cloudways SSH Password sail-knowledge 10 2
Semrush API Key sail-knowledge 2 2

No sk-, sk-ant-, ghp_, github_pat_, xoxb-, or AKIA token literals found in any committed file or recent diff. Anthropic, OpenAI, GitHub, Slack, AWS credentials are clean.

QA Recommendations Pending Approval

Five items awaiting Sam's decision (full A/B/C/D options in the Codex log):