admin
c01deca048
CI (SIAX Cloud) / sonar (pull_request) Skipped
masterplan-lock / check (push) Successful in 5s
masterplan-lock / check (pull_request) Successful in 10s
CI (SIAX Cloud) / security (pull_request) Successful in 19s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 21s
CI (SIAX Cloud) / integration (pull_request) Successful in 40s
CI (SIAX Cloud) / quality (pull_request) Successful in 2m13s
- One run per ref (concurrency) for CI, security, nightly and release; branch pushes no longer duplicate pull_request runs (push is main-only). - Deploys keep their own concurrency group so two runs never race Coolify. - pnpm store cache on every Node job. - New /api/version returns the deployed commit (no secrets). - New scheduled prod-smoke workflow: readiness, db/stripe health, running commit == main, and the document/credit routes exist (401/405, never 5xx).
44 lines
1.7 KiB
YAML
44 lines
1.7 KiB
YAML
name: Security Scan (SIAX Cloud)
|
|
|
|
# Security scanning on every push/PR + weekly re-run.
|
|
#
|
|
# This job runs the same Trivy invocation as ci.yml's `security` job and
|
|
# previously carried the same defect: `--exit-code 0` meant it could report
|
|
# success while holding a CRITICAL finding (measured 2026-09-08 with a
|
|
# planted AWS secret key -- detected, still exit 0). Its context
|
|
# "Security Scan (SIAX Cloud) / security" is NOT in branch protection's
|
|
# required list, so this one never gated a merge either way; it is fixed
|
|
# here so a green tick on this workflow means what a reader assumes it
|
|
# means. See ci.yml's `security` job for the measurement and for the
|
|
# services/scrapers unpinned-requirements coverage gap.
|
|
#
|
|
# NOTE: findings on services/scrapers/* (FlareSolverr/Tor/curl_cffi) are
|
|
# expected and out of scope for CI gating -- kept per the account owner's
|
|
# dated, attributed decision (Simon Axelsson, 2026-08-11, interactive
|
|
# prompt; no rationale beyond "keep it" given or invented). See SECURITY.md
|
|
# and docs/compliance/GOLDEN-STANDARD-REPORT.md control C6 for full context.
|
|
on:
|
|
push:
|
|
branches: ["main"]
|
|
pull_request:
|
|
workflow_dispatch:
|
|
schedule:
|
|
- cron: "0 5 * * 1" # weekly Monday re-scan
|
|
|
|
|
|
concurrency:
|
|
group: security-${{ github.ref }}
|
|
cancel-in-progress: true
|
|
jobs:
|
|
security:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 15
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
- name: Install Trivy
|
|
run: |
|
|
curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
|
|
- name: Trivy fs scan (vuln + secrets -- fails on HIGH/CRITICAL)
|
|
run: |
|
|
trivy fs --scanners vuln,secret --severity HIGH,CRITICAL --exit-code 1 --skip-dirs 'siax/sbom' .
|