Skip to content

security: verify and improve supply-chain.md #302

Closed

Description

@homer6

Turn the imported docs/security/supply-chain.md (build inputs, provenance, release evidence) into a verified page.

  • Check every claim against a primary source (vendor docs, cppreference, CERT, OWASP, papers); fix or remove what doesn't hold, and say so in the PR.
  • Cite the Core Guidelines rule IDs and SEI CERT rule IDs (IDs and links only; don't copy CERT text).
  • Replace or add examples of our own, compile-checked, and tests in tests/security/ where a claim can be checked.
  • Link the safety foundations (docs/guidelines/safety.md, the docs/examples/ pages) instead of repeating them.
  • Positive framing: what makes C++ code secure.

Specific: SLSA, SBOMs, signing, pinned dependencies; this repo's own practice (actions pinned by SHA, manual CI, release evidence) as the example.

Part of #286. PR into dev-0.5, from a feature branch in its own worktree.

Activity

  1. self-assigned this
    on Nov 3, 2026
  2. homer6 commented on Nov 3, 2026

    @homer6
    OwnerAuthor

    Delivered in #334.

    How it was solved

    • supply-chain.md rewritten and verified: pin by content (with a table per input kind), SBOMs, SLSA v1.2 build isolation, reproducible-build flags (checked on GCC 15 / Clang 22), signing and verification, release evidence, and this repo's practice.
    • The page found two gaps in the repo itself, both fixed: GoogleTest is now pinned by commit hash rather than tag, and CI checks the apt.llvm.org key fingerprint.
    • tests/security/supply-chain_test.cpp keeps the pins honest.

    How to test

    • ctest --preset clang-22 -L '^security$': SecuritySupplyChain.* pass
    • Fresh configure: git -C build/<preset>/_deps/googletest-src rev-parse HEAD is 063de7e9…
    • Next consented linux.yml run: clang-apt-llvm jobs pass the key check

    Re-open if review rejects the PR or validation surfaces a regression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

securityv0.5.0 security work

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions