Repository navigation
Description
v0.5.0 is about helping users write secure C++: code that holds up against an adversary (trust boundaries, untrusted input, secrets, attack surface, hardening, verification, supply chain). Security is not the same as safety: docs/guidelines/safety.md covers correctness and memory safety; docs/security/ builds on it and links to it where a safety defect is the attack path.
Framing: C++ written to the Core Guidelines (explicit ownership, bounded interfaces, checked conversions, the type/bounds/lifetime profiles) and verified with analysis, sanitizers and fuzzing is the path to secure code. The pages never present C++ as "not memory-safe".
Branching: work lands on dev-0.5 (forked from dev at ddf1dfa). Each issue gets a feature branch in its own worktree and a PR into dev-0.5. dev-0.5 is rebased onto dev when dev moves.
Plan:
- Import the owner's research report ("Security Practices for Modern C++") into
docs/security/, one page per section, nearly as written (the owner chose import-then-fix). - Verify and improve each page: check claims against primary sources, cite Core Guidelines and SEI CERT rule IDs, add our own tested examples (
tests/security/<page>_test.cpp), link the safety foundations. - Prove the claims across platforms: hardened build presets and CI jobs, death tests that show hardening fires, fuzz harnesses, clang-tidy.
- Make the skills and docs use it: security review in
modern-cpp/cpp-guidelines, evals, CLAUDE.md, platform report.
The checklist of child issues follows below.
Checklist
1. Import
2. Verify and improve each page
- security: verify and improve README.md + language-versions.md #288
- security: verify and improve threat-modeling.md #289
- security: verify and improve ownership-and-lifetime.md #290
- security: verify and improve bounds.md #291
- security: verify and improve integers.md #292
- security: verify and improve object-representation.md #293
- security: verify and improve parsing-and-validation.md #294
- security: verify and improve concurrency.md #295
- security: verify and improve error-handling.md #296
- security: verify and improve cryptography-and-secrets.md #297
- security: verify and improve filesystem-and-processes.md #298
- security: verify and improve resource-limits.md #299
- security: verify and improve hardening.md #300
- security: verify and improve verification.md #301
- security: verify and improve supply-chain.md #302
- security: verify and improve deployment.md #303
- security: verify and improve policy.md #304
3. Prove it across platforms
- security: hardened build presets and CI jobs (CPPDOCS_HARDEN) #305
- security: death tests proving library hardening fires #306
- security: fuzz harnesses and a CI fuzz smoke run #307
- security: clang-tidy config and CI job #308
4. Skills and docs
- security: a /cpp-security skill for the security knowledge #312 (the /cpp-security skill; first version after security: verify and improve README.md + language-versions.md #288)
- security: security review in the modern-cpp and cpp-guidelines skills, with evals #309
- security: CLAUDE.md and README for docs/security and the dev-0.5 workflow #310
Activity
homer6 commentedon Nov 4, 2026
Shipped in v0.5.0: https://github.com/homer6/cpp-docs/releases/tag/v0.5.0 (release PR #389, tag on
f97b4608). Every child issue is closed;docs/security/is onmain, with the hardened, fuzz and clang-tidy CI jobs and the security skill. Follow-ups outside the epic: #354 (UBSan in the Apple fuzz build), #313 (contracts status).