Skip to content

fix: tighten workflow permissions, add security hardening, and fix uv tool invocations#431

Merged
jmeridth merged 2 commits intomainfrom
fix/tighten-workflow-permissions-add-security-hardening
Mar 14, 2026
Merged

fix: tighten workflow permissions, add security hardening, and fix uv tool invocations#431
jmeridth merged 2 commits intomainfrom
fix/tighten-workflow-permissions-add-security-hardening

Conversation

@jmeridth
Copy link
Collaborator

What

Move elevated permissions from workflow level to job level across three workflows (mark-ready-when-ready, scorecard, stale) so each job only holds the permissions it actually needs. Add step-security/harden-runner to all eight workflows that define steps. Add CodeQL SAST scanning and dependency-review workflows. Add pre-commit configuration with gitleaks, formatting hooks, and local linter hooks. Fix Makefile to invoke flake8, pytest, pylint, and mypy via uv run python -m since they lack console script entry points in the uv venv. Upgrade PyJWT from 2.11.0 to 2.12.1 to address CVE-2026-32597.

Why

Workflow-level write permissions apply to every job in the workflow, granting broader access than necessary. Moving them to job level follows the principle of least privilege. Harden-runner audits outbound network calls from GitHub-hosted runners, improving supply-chain visibility. CodeQL and dependency-review close gaps in static analysis and vulnerable-dependency detection. The Makefile commands failed under uv because those packages don't install console scripts; python -m ensures the tools are always found. PyJWT <= 2.11.0 doesn't validate the RFC 7515 crit header parameter (CVSS 7.5).

Notes

  • The uv run to uv run python -m change also affects CI since python-ci calls make lint and make test
  • release.yml, auto-labeler.yml, and pr-title.yml use reusable workflows at the job level so harden-runner cannot be added there; it must go in the reusable workflow definitions instead
  • The scorecard workflow previously used permissions: read-all which granted read access to all scopes; now explicitly scoped to only what's needed
  • PyJWT is a transitive dependency; verify downstream consumers aren't relying on the old crit-header-ignored behavior

@jmeridth jmeridth requested a review from zkoppert as a code owner March 14, 2026 02:00
Copilot AI review requested due to automatic review settings March 14, 2026 02:00
@github-actions github-actions bot added the fix label Mar 14, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves the repository’s security posture and CI reliability by tightening GitHub Actions permissions, adding runner hardening, introducing additional security workflows, and ensuring Python tooling runs consistently under uv.

Changes:

  • Move elevated GitHub Actions permissions from workflow-level to job-level (least privilege) and add step-security/harden-runner to workflows with steps.
  • Add new security workflows: CodeQL scanning and dependency review for PRs.
  • Fix make lint / make test tool execution under uv by invoking tools via uv run python -m ..., and add a pre-commit configuration (including gitleaks).

Reviewed changes

Copilot reviewed 12 out of 13 changed files in this pull request and generated no comments.

Show a summary per file
File Description
uv.lock Updates PyJWT lock entry to 2.12.1.
Makefile Runs pytest/flake8/pylint/mypy via uv run python -m ... for consistent tool resolution.
.pre-commit-config.yaml Adds pre-commit hooks (gitleaks + whitespace fixes + local Python format/lint hooks via uv).
.github/workflows/super-linter.yaml Adds harden-runner audit step before workflow actions.
.github/workflows/stale.yml Moves issue/PR permissions to the job and adds harden-runner.
.github/workflows/scorecard.yml Replaces read-all with scoped permissions and adds harden-runner.
.github/workflows/python-ci.yml Adds harden-runner to test/lint workflow.
.github/workflows/mark-ready-when-ready.yml Moves elevated permissions to the job and adds harden-runner.
.github/workflows/docker-ci.yml Adds harden-runner to the Docker build workflow.
.github/workflows/dependency-review.yml Adds a dependency-review workflow (with harden-runner).
.github/workflows/copilot-setup-steps.yml Adds harden-runner to Copilot setup workflow.
.github/workflows/contributors_report.yaml Adds harden-runner to the monthly report workflow.
.github/workflows/codeql.yml Adds a CodeQL workflow (with harden-runner) for Python scanning.

@jmeridth jmeridth force-pushed the fix/tighten-workflow-permissions-add-security-hardening branch from 1c1909c to d061d9d Compare March 14, 2026 02:03
… tool invocations

## What

Move elevated permissions from workflow level to job level across three workflows
(mark-ready-when-ready, scorecard, stale) so each job only holds the permissions it
actually needs. Add step-security/harden-runner to all eight workflows that define steps.
Add CodeQL SAST scanning and dependency-review workflows. Add pre-commit configuration
with gitleaks, formatting hooks, and local linter hooks. Fix Makefile to invoke flake8,
pytest, pylint, and mypy via `uv run python -m` since they lack console script entry
points in the uv venv. Upgrade PyJWT from 2.11.0 to 2.12.1 to address CVE-2026-32597.

## Why

Workflow-level write permissions apply to every job in the workflow, granting broader
access than necessary. Moving them to job level follows the principle of least privilege.
Harden-runner audits outbound network calls from GitHub-hosted runners, improving
supply-chain visibility. CodeQL and dependency-review close gaps in static analysis and
vulnerable-dependency detection. The Makefile commands failed under uv because those
packages don't install console scripts; `python -m` ensures the tools are always found.
PyJWT <= 2.11.0 doesn't validate the RFC 7515 `crit` header parameter (CVSS 7.5).

## Notes

- The `uv run` to `uv run python -m` change also affects CI since python-ci calls `make lint` and `make test`
- release.yml, auto-labeler.yml, and pr-title.yml use reusable workflows at the job level so harden-runner cannot be added there; it must go in the reusable workflow definitions instead
- The scorecard workflow previously used `permissions: read-all` which granted read access to all scopes; now explicitly scoped to only what's needed
- PyJWT is a transitive dependency; verify downstream consumers aren't relying on the old crit-header-ignored behavior

Signed-off-by: jmeridth <jmeridth@gmail.com>
@jmeridth jmeridth force-pushed the fix/tighten-workflow-permissions-add-security-hardening branch from d061d9d to 9c78dcb Compare March 14, 2026 02:27
@zkoppert
Copy link
Collaborator

The Autobuild step in codeql.yml is a no-op for Python since CodeQL analyzes source directly without a build step. Please remove the Autobuild step and its surrounding comments to keep the workflow clean.

Signed-off-by: jmeridth <jmeridth@gmail.com>
Copy link
Collaborator

@zkoppert zkoppert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - minor note: consider removing the Autobuild step from codeql.yml since it's a no-op for Python.

@jmeridth jmeridth merged commit faef7c7 into main Mar 14, 2026
36 checks passed
@jmeridth jmeridth deleted the fix/tighten-workflow-permissions-add-security-hardening branch March 14, 2026 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants