feat: Python project scan reusable workflow

.github/workflows/scan-python.yaml

@@ -0,0 +1,145 @@
+name: Run security scans for a Python project
+
+on:
+  workflow_call:
+    inputs:
+      packages:
+        required: false
+        type: string
+        description: |
+          Packages to install with apt when building the wheel or scanning with trivy
+          This can be useful if creating a virtual environment has extra build-deps.
+      requirements-find-args:
+        required: false
+        type: string
+        default: ''
+        description: |
+          Additional arguments to use for find when finding requirements files. Can
+          be used to find additional files or to exclude files.
+      osv-extra-args:
+        required: false
+        type: string
+        default: ''
+        description: |
+          Additional arguments to pass to osv-scanner.
+
+jobs:
+  build-artefacts:
+    name: Build artefacts
+    runs-on: [ubuntu-24.04] # Needs Noble specifically
+    steps:
+      - name: Install tools
+        shell: bash
+        run: |
+          uv_job=$(sudo snap install --no-wait --classic astral-uv)
+          sudo apt-get update
+          sudo apt-get --yes install python3-venv python3-build ${{ inputs.packages }}
+          snap watch $uv_job
+          mkdir -p ${{ runner.temp }}/python-artefacts/requirements
+      - name: Checkout source
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Find any existing requirements files
+        shell: bash
+        run: |
+          find -type f -name 'requirements*.txt' ${{ inputs.requirements-find-args }} -exec cp '{}' "${{ runner.temp }}/python-artefacts/requirements" \;
+      - name: Build wheel
+        shell: bash
+        run: |
+          python -m build --wheel --outdir ${{ runner.temp }}/python-artefacts
+      - name: Create requirements files from uv
+        if: ${{ hashFiles('uv.lock') != '' }}
+        run: |
+          uv export --frozen --no-editable --no-emit-workspace --format=requirements-txt --output-file=${{ runner.temp }}/python-artefacts/requirements/uv-requirements.txt
+          uv export --frozen --no-editable --no-emit-workspace --format=requirements-txt --all-extras --output-file=${{ runner.temp }}/python-artefacts/requirements/uv-requirements-all.txt
+      - name: Upload artefacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: artefacts
+          path: ${{ runner.temp }}/python-artefacts
+  scan-trivy:
+    name: Trivy
+    needs: build-artefacts
+    runs-on: [ubuntu-latest]
+    steps:
+      - name: Install tools
+        run: |
+          trivy_job=$(sudo snap install --no-wait trivy)
+          uv_job=$(sudo snap install --no-wait --classic astral-uv)
+          sudo apt-get update
+          sudo apt-get --yes install ${{ inputs.packages }}
+          snap watch $trivy_job
+          snap watch $uv_job
+      - name: Checkout source
+        uses: actions/checkout@v4
+        with:
+          path: source
+      - name: Download artefacts
+        uses: actions/download-artifact@v4
+        with:
+          name: artefacts
+      - name: Scan requirements files
+        if: ${{ !cancelled() && hashFiles('requirements/') != '' }}
+        run: |
+          for reqs in $(ls -1 requirements/*); do
+            trivy filesystem "${reqs}"
+          done
+      - name: Scan wheel files
+        if: ${{ !cancelled() && hashFiles('*.whl') != '' }}
+        run: |
+          for wheel in $(ls -1 *.whl); do
+            echo "::group::Scanning ${wheel}"
+            wheel_dir=$(mktemp -d --tmpdir=${{ runner.temp }} --suffix=.whl-dir)
+            unzip -q "${wheel}" -d "${wheel_dir}"
+            trivy filesystem "${wheel_dir}"
+            echo "::endgroup::"
+          done
+      - name: Scan source
+        if: ${{ !cancelled() }}
+        run: |
+          trivy filesystem source
+      - name: Scan virtual environments
+        run: |
+          snap watch --last=install
+          for reqs in $(ls -1 requirements/*); do
+            echo "::group::Setup..."
+            venv=$(mktemp -d --tmpdir=${{ runner.temp }} --suffix=.venv)
+            uv venv "${venv}"
+            source "${venv}/bin/activate"
+            echo Installing "${reqs}"
+            uv pip install --requirement="${reqs}"
+            echo "::endgroup::"
+            for wheel in $(ls -1 *.whl); do
+              uv pip install "${wheel}"
+              trivy filesystem "${venv}"
+            done
+            deactivate
+          done
+  scan-osv:
+    name: OSV-scanner
+    needs: build-artefacts
+    runs-on: [ubuntu-latest]
+    steps:
+      - name: Install tools
+        run: |
+          sudo snap install osv-scanner
+          sudo snap install --no-wait --classic astral-uv
+      - name: Checkout source
+        uses: actions/checkout@v4
+        with:
+          path: source
+      - name: Download artefacts
+        uses: actions/download-artifact@v4
+        with:
+          name: artefacts
+      - name: Scan requirements files
+        if: ${{ !cancelled() && hashFiles('requirements/') != '' }}
+        run: |
+          for reqs in $(ls -1 requirements/*); do
+            osv-scanner ${{ inputs.osv-extra-args }} --lockfile requirements.txt:${reqs}
+          done
+      - name: Scan source
+        if: ${{ !cancelled() }}
+        run: |
+          osv-scanner source

README.md

@@ -1,3 +1,62 @@
 # starflow
 
 Starcraft team GHA Workflows
+
+# Reusable Workflows
+
+Some of these automations are provided as [Reusable workflows](https://docs.github.com/en/actions/sharing-automations/reusing-workflows).
+For these workflows, you can embed them in a workflow you run at the `job` level.
+Examples are provided below.
+
+## Python security scanner
+
+The Python security scanner workflow uses several tools (trivy, osv-scanner) to scan a
+Python project for security issues. It does the following:
+
+1. Creates a wheel of the project.
+2. Exports a `uv.lock` file (if present in the project) as two requirements files:
+   a. `requirements.txt` with no extras
+   b. `requirements-all.txt` with all available extras
+
+If there are any existing `requirements*.txt` files in your project, it will scan those
+below too.
+
+With [Trivy](https://github.com/aquasecurity/trivy), it:
+
+1. Scans the requirements files
+2. Scans the wheel file(s)
+3. Scans the project directory
+4. Installs each combination of (requirements, wheel) in a virtual environment and scans that environment.
+
+With [OSV-scanner](https://google.github.io/osv-scanner/) it:
+
+1. Scans the requirements files
+2. Scans the project directory
+
+### Usage
+
+An example workflow for your own Python project that will use this workflow:
+
+```yaml
+name: Security scan
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - hotfix/*
+
+jobs:
+  python-scans:
+    name: Scan Python project
+    uses: canonical/starflow/.github/workflows/scan-python.yaml@main
+    with:
+      # Additional packages to install on the Ubuntu runners for building
+      packages: python-apt-dev cargo
+      # Additional arguments to `find` when finding requirements files.
+      # This example ignores 'requirements-noble.txt'
+      requirements-find-args: '! -name requirements-noble.txt'
+      # Additional arguments to pass to osv-scanner.
+      # This example adds configuration from your project.
+      osv-extra-args: '--config=source/osv-scanner.toml'
+```