Files

T

malkuthro 2babbafb6b chore(security): pin Actions and harden test lock (#273 )

* chore(security): pin Actions and update aiohttp

* fix(security): generate universal test lock

* fix(security): harden relock safeguards

2026-08-06 20:02:37 +02:00

2.9 KiB

Raw Blame History

Dependency security

This project treats the locked test dependency set as the dependency-review surface. Local bootstrap, pull-request CI, and the weekly scheduled audit all check constraints-test.txt with pip-audit.

What gets audited

constraints-test.txt pins the [test] extras from pyproject.toml plus their transitive dependencies.
The bootstrap scripts install the test extras against that lock, then run pip-audit on the installed environment.
CI audits the committed lock with pip-audit -r constraints-test.txt on each pull request and on a weekly schedule, so newly disclosed CVEs in old pins are caught even when nobody has touched the dependency files. It also strips environment markers into a temporary manifest and audits that manifest, so Windows-only and Linux-only pins are each checked.
Bandit remains a separate first-party-code scan. A green Bandit job does not mean the dependency lock is clean.

GitHub Actions

Every third-party uses: reference in .github/workflows/ is pinned to an immutable commit SHA, with its source release or branch reference left in a comment for readability. When updating an Action, resolve that reference to a commit with the GitHub API, review the change in the PR, then update both the SHA and its comment together. Do not use mutable major-version tags such as @v3 or @v7 in committed workflows.

Dependabot groups all GitHub Action updates into one weekly pull request. Python test dependencies are updated through the deliberate universal relock below, so the complete cross-platform lock diff stays one reviewable security unit.

Regenerating the lock

Regenerate the lock only as an intentional dependency-change PR. The bootstrap uses uv to resolve a universal Python 3.11 lock, including the conditional dependencies needed by both CI platforms. The scripts check that uv is available before replacing an existing .venv, then use --upgrade so the relock can move stale vulnerable pins. Install uv before relocking if it is not already available.

scripts\bootstrap_test_env.ps1 -Force -Relock

bash scripts/bootstrap_test_env.sh --force --relock

Review and commit the resulting constraints-test.txt diff. Do not hand-edit individual pins.

Responding to a CVE

Open or update a dependency-security issue with the vulnerable package, affected version, fixed version, and audit output.
Relock with the commands above.
Confirm pip-audit reports no known vulnerabilities.
Run the focused bootstrap/CI contract tests:

.\.venv\Scripts\python -m pytest tests\scripts\test_bootstrap_constraints.py -q

If the relock changes more than the vulnerable package and normal transitive bumps, call that out in the PR description so reviewers know what to inspect.

Use -NoAudit / --no-audit only for explicit offline troubleshooting. Do not merge a dependency lock that has not passed the audit gate.

2.9 KiB Raw Blame History