~/sang

CI security gate for this site

GitHub ActionsCodeQLgitleaksnpm auditCycloneDXDependabotOWASP ZAPDockeraxe-coreLighthouse CI

Problem: a personal site is easy to ship once and let drift, and I built this one with an AI assistant, so I cannot vouch for it by having written every line. I wanted evidence that fails loudly instead of trust.

Approach: run a fixed set of checks on every push to main and every pull request, and keep the pipeline itself tight.

Outcome: every change to the site runs through the same set of checks. The write-up, A security gate for a personal site, built with an AI assistant, covers how it was built and where it falls short.

What it does not do yet: on a free private repository GitHub offers no branch protection, so passing checks are a habit and not a requirement. CodeQL results are not uploaded to GitHub, nothing actively attacks the running site (the ZAP scan is passive), and the SBOM is neither signed nor attested. I plan to add SonarCloud (SAST), Snyk (SCA) and Renovate, none of which is set up yet.

guest@sang:~$