Harden workflow egress policies and pin @playwright/mcp version by Copilot · Pull Request #694 · Hack23/riksdagsmonitor

Copilot · 2026-03-01T01:52:46Z

Hardens GitHub Actions workflows by upgrading from egress-policy: audit to egress-policy: block with explicit allowed endpoints, and reduces supply chain risk by pinning @playwright/mcp@latest to a specific version.

Changes Made

Egress Policy Hardening

Switched egress-policy from audit to block with allowed-endpoints in quality-checks.yml (4 jobs), javascript-testing.yml (4 jobs), and lighthouse-ci.yml (1 job)
Used folded YAML style (>) for allowed-endpoints to match the working deploy-s3.yml reference pattern — the Go harden-runner agent v0.14.3 parses endpoints using spaces as delimiters, so > (folded) is required; | (literal) bundles all entries into one invalid token
Added codeload.github.com:443 to all jobs using actions/checkout
Renamed summary job step from Audit all outbound calls → Harden Runner (block outbound calls) to reflect enforced behavior
Removed unnecessary apt-get install jq step (jq is pre-installed on ubuntu-latest), eliminating the deb.debian.org:80 plaintext HTTP endpoint from the allowlist
Removed allowed-endpoints entirely from the summary job in quality-checks.yml — it only runs echo commands and requires zero external network access

Allowlist Completeness

Added data.riksdagen.se:443 and www.riksdagen.se:443 to the link-checker job in quality-checks.yml
Added fonts.googleapis.com:443 and fonts.gstatic.com:443 to lighthouse-ci.yml (the site loads Google Fonts; required for accurate Lighthouse audit results)
Added all remaining external domains linked from riksdagsmonitor.com to the link-checker's allowed-endpoints: www.hack23.com:443, www.linkedin.com:443, cia.sourceforge.io:443, data.worldbank.org:443, raw.githubusercontent.com:443, www.esv.se:443, and www.val.se:443
Added download.cypress.io:443 to the multi-language-sanity Cypress job in javascript-testing.yml — Cypress binary downloads can originate from this host as well as cdn.cypress.io

Dependency Pinning

Pinned @playwright/mcp from @latest to @0.0.68 in news-article-generator.md, news-evening-analysis.md, and news-realtime-monitor.md
Updated corresponding .lock.yml files to match the pinned version

Security Impact

Reduces supply chain attack surface by pinning @playwright/mcp
Enforces network egress controls (TLS-only endpoints) instead of audit-only monitoring
Removes plaintext HTTP egress (deb.debian.org:80) from all allowlists
Summary job allowlist tightened to zero endpoints (least-privilege: no network access needed)
Compliant with CIS Controls v8.1 Control 2 (Software Asset Management)

Testing

All 2255 tests pass — no regressions
YAML syntax verified for all modified workflow files

Original prompt

This section details on the original issue you should resolve

<issue_title>Harden workflow egress policies and pin @playwright/mcp version</issue_title>
<issue_description>## 📋 Issue Type
Security / DevSecOps

🎯 Objective

Harden GitHub Actions workflows by upgrading from egress-policy: audit to egress-policy: block with explicit allowed endpoints, and pin the @playwright/mcp@latest dependency to a specific version.

📊 Current State

Egress policy: Most workflows (26+ instances) use egress-policy: audit which only monitors network traffic. Only deploy-s3.yml uses egress-policy: block with explicit allowed endpoints.

Unpinned dependency: All 10 news workflows use @playwright/mcp@latest in their MCP tools configuration, which is vulnerable to supply chain attacks.

Unpinned MCP packages: @smithery/cli@4.4.0 is version-pinned but @playwright/mcp@latest is not.

🚀 Desired State

All CI/CD workflows use egress-policy: block with minimum necessary allowed endpoints

@playwright/mcp pinned to a specific version (e.g., @playwright/mcp@0.0.29)

Supply chain attack surface reduced

Compliant with CIS Controls v8.1 (Control 2: Inventory and Control of Software Assets)

🔧 Implementation Approach

Audit egress traffic for each workflow using existing egress-policy: audit logs

Create allowed-endpoints lists for each workflow

Switch from audit to block gradually (one workflow at a time)

Pin @playwright/mcp to a specific version in all 10 news workflow .md files

Update corresponding .lock.yml files via workflow compilation

Priority order:

quality-checks.yml (most frequent)

javascript-testing.yml (critical for CI)

lighthouse-ci.yml

News workflows (10 files)

🤖 Recommended Agent

security-architect — Supply chain security hardening

✅ Acceptance Criteria

All workflows use egress-policy: block with explicit allowed-endpoints

@playwright/mcp pinned to specific version in all news workflow .md files

All workflows pass after hardening

No legitimate network requests blocked

📚 References

Current blocked workflow: .github/workflows/deploy-s3.yml (reference pattern)

Step Security docs: https://github.com/step-security/harden-runner

ISMS Policy: Secure Development Policy

CIS Controls v8.1: Control 2 (Software Asset Management)

🏷️ Labels

type:security, priority:high, component:ci-cd</issue_description>

<agent_instructions>Harden workflows by upgrading egress-policy from audit to block with explicit allowed-endpoints. Start with quality-checks.yml and javascript-testing.yml. Also pin @playwright/mcp to a specific version in all news workflow .md files.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Fixes Harden workflow egress policies and pin @playwright/mcp version #675

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

- Upgrade egress-policy from audit to block in quality-checks.yml (4 jobs) - Upgrade egress-policy from audit to block in javascript-testing.yml (4 jobs) - Upgrade egress-policy from audit to block in lighthouse-ci.yml (1 job) - Add explicit allowed-endpoints for each job based on required network access - Pin @playwright/mcp@latest to @playwright/mcp@0.0.68 in 3 news workflow .md files - Update corresponding .lock.yml files to match pinned playwright/mcp version Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>

github-actions · 2026-03-01T02:58:57Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

Copilot

Pull request overview

Hardens select GitHub Actions workflows by switching Step Security’s runner hardening from audit-only to enforced egress blocking with allowlists, and reduces supply-chain risk by pinning @playwright/mcp to an explicit version in news workflows.

Changes:

Switched egress-policy from audit to block with allowed-endpoints in quality-checks.yml, javascript-testing.yml, and lighthouse-ci.yml.
Pinned @playwright/mcp from @latest to @0.0.68 across three news workflow sources and their compiled lock files.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
.github/workflows/quality-checks.yml	Enforces blocked egress with per-job endpoint allowlists (plus a summary job allowlist).
.github/workflows/javascript-testing.yml	Enforces blocked egress with allowlists, including Cypress CDN for the Cypress job.
.github/workflows/lighthouse-ci.yml	Enforces blocked egress with allowlists for site + GCS usage.
.github/workflows/news-realtime-monitor.md	Pins `@playwright/mcp` version in MCP tool configuration.
.github/workflows/news-realtime-monitor.lock.yml	Updates compiled workflow to match pinned `@playwright/mcp` version.
.github/workflows/news-evening-analysis.md	Pins `@playwright/mcp` version in MCP tool configuration.
.github/workflows/news-evening-analysis.lock.yml	Updates compiled workflow to match pinned `@playwright/mcp` version.
.github/workflows/news-article-generator.md	Pins `@playwright/mcp` version in MCP tool configuration.
.github/workflows/news-article-generator.lock.yml	Updates compiled workflow to match pinned `@playwright/mcp` version.

Copilot · 2026-03-01T03:01:09Z

.github/workflows/quality-checks.yml

      - name: Harden the runner (Audit all outbound calls)
        uses: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b # v2.15.0
        with:
-          egress-policy: audit
+          egress-policy: block
+          allowed-endpoints: >
+            api.github.com:443
+            github.com:443


The step name says 'Audit all outbound calls' but the config is now egress-policy: block. Rename the step to reflect the enforced behavior (e.g., 'Harden runner (block outbound calls)') to avoid confusion when reading logs.

Fixed in 0fb0dc7 — renamed to Harden Runner (block outbound calls).

Copilot · 2026-03-01T03:01:09Z

.github/workflows/quality-checks.yml

+          egress-policy: block
+          allowed-endpoints: >
+            api.github.com:443
+            github.com:443
+            nodejs.org:443
+            objects.githubusercontent.com:443
+            registry.npmjs.org:443


Using YAML folded style (>) will fold newlines into spaces, producing a single-line string. If step-security/harden-runner expects newline-delimited endpoints, this can cause the allowlist to be misparsed. Prefer literal style (|) to preserve line breaks for endpoint lists.

Fixed in 0fb0dc7 — switched all allowed-endpoints blocks from folded style (>) to literal style (|) across all three workflows.

Copilot · 2026-03-01T03:01:09Z

.github/workflows/javascript-testing.yml

+          egress-policy: block
+          allowed-endpoints: >
+            api.github.com:443
+            github.com:443


actions/checkout typically downloads the repository archive from codeload.github.com (not github.com). With egress-policy: block, the checkout step can fail unless codeload.github.com:443 is included in allowed-endpoints for jobs that use actions/checkout.

Suggested change

github.com:443

github.com:443

codeload.github.com:443

Fixed in 0fb0dc7 — added codeload.github.com:443 to every job that uses actions/checkout (3 jobs in quality-checks.yml, 3 in javascript-testing.yml, 1 in lighthouse-ci.yml).

pethers · 2026-03-01T03:36:06Z

@copilot apply changes based on the comments in this thread

github-actions · 2026-03-01T03:36:49Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

- Fix step name: 'Harden the runner (Audit all outbound calls)' -> 'Harden Runner (block outbound calls)' - Change allowed-endpoints YAML from folded style (>) to literal style (|) in all 3 workflows - Add codeload.github.com:443 to all jobs using actions/checkout (9 jobs across 3 workflows) Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>

Copilot

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Copilot · 2026-03-01T12:28:29Z

.github/workflows/quality-checks.yml

+            objects.githubusercontent.com:443
+            registry.npmjs.org:443
+            riksdagsmonitor.com:443
+            www.riksdagen.se:443


The link-checker job runs linkinator https://riksdagsmonitor.com/ and (per the current --skip regex) will attempt to validate external links on the homepage beyond the riksdagen.se domains (e.g., links to www.hack23.com and www.linkedin.com are present in index.html). With egress-policy: block, those requests will be blocked and inflate the external-links report with false failures. Either add the relevant domains (e.g., www.hack23.com:443, www.linkedin.com:443) to allowed-endpoints, or extend the --skip pattern to exclude them so the report reflects real link issues rather than egress blocks.

Suggested change

www.riksdagen.se:443

www.riksdagen.se:443

www.hack23.com:443

www.linkedin.com:443

Fixed in c620e77 — added www.hack23.com:443 and www.linkedin.com:443 as requested, plus all other external domains linked from index.html that would be blocked: cia.sourceforge.io:443, data.worldbank.org:443, raw.githubusercontent.com:443, www.esv.se:443, and www.val.se:443.

pethers · 2026-03-01T12:40:47Z

@copilot apply changes based on the comments in this thread

github-actions · 2026-03-01T12:41:53Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

Add all external domains linked from riksdagsmonitor.com that the linkinator external check would visit: - www.hack23.com:443 and www.linkedin.com:443 (per review comment) - cia.sourceforge.io:443, data.worldbank.org:443 - raw.githubusercontent.com:443, www.esv.se:443, www.val.se:443 Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>

Copilot · 2026-03-01T12:43:58Z

@copilot apply changes based on the comments in this thread

Done in c620e77 — added all missing external domains to the link-checker's allowed-endpoints.

github-actions · 2026-03-01T13:07:47Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

Copilot

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Copilot · 2026-03-01T13:11:15Z

.github/workflows/quality-checks.yml

+          allowed-endpoints: >
+            api.github.com:443
+            github.com:443


The summary job appears to only emit a local summary (no checkout/install shown in this hunk), but it still permits outbound access to GitHub/API. If the job truly doesn’t require network egress, tightening this to an empty allowlist (or removing allowed-endpoints entirely, depending on the action’s expectations) would reduce the allowed attack surface.

Suggested change

allowed-endpoints: >

api.github.com:443

github.com:443

Fixed in 813c03e — removed the allowed-endpoints block entirely from the summary job. It only runs echo commands with no network access needed.

Copilot · 2026-03-01T13:11:15Z

.github/workflows/javascript-testing.yml

+          egress-policy: block
+          allowed-endpoints: >
+            api.github.com:443
+            cdn.cypress.io:443
+            codeload.github.com:443
+            github.com:443
+            nodejs.org:443
+            objects.githubusercontent.com:443
+            registry.npmjs.org:443


Cypress installs commonly download the binary from download.cypress.io (and/or related hosts) rather than only cdn.cypress.io. If this job performs a fresh Cypress install/download, the current allowlist may block it. Consider adding download.cypress.io:443 (or confirming the exact host(s) used by the Cypress download in this workflow) to avoid intermittent failures on cold caches.

Fixed in 813c03e — added download.cypress.io:443 to the multi-language-sanity job's allowlist alongside the existing cdn.cypress.io:443.

pethers · 2026-03-01T13:29:27Z

@copilot apply changes based on the comments in this thread

github-actions · 2026-03-01T13:30:34Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

- Remove allowed-endpoints from summary job in quality-checks.yml: the job only runs echo commands and needs zero external network access - Add download.cypress.io:443 to multi-language-sanity Cypress job in javascript-testing.yml: Cypress binary downloads can originate from download.cypress.io as well as cdn.cypress.io Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>

Copilot · 2026-03-01T13:32:05Z

@copilot apply changes based on the comments in this thread

Done in 813c03e — both changes applied: summary job allowed-endpoints removed (zero network access needed), and download.cypress.io:443 added to the Cypress job.

github-actions · 2026-03-01T13:39:19Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

Copilot

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated no new comments.

github-actions · 2026-03-01T13:49:24Z

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json

Copilot AI assigned Copilot and pethers Mar 1, 2026

Copilot AI mentioned this pull request Mar 1, 2026

Comprehensive codebase analysis: 18 issues created and assigned to Copilot #671

Draft

Copilot started work on behalf of pethers March 1, 2026 02:03 View session

Copilot AI changed the title ~~[WIP] Harden workflow egress policies and pin playwright/mcp version~~ Harden workflow egress policies and pin @playwright/mcp version Mar 1, 2026

Copilot finished work on behalf of pethers March 1, 2026 02:15

Merge branch 'main' into copilot/harden-egress-policies

dcc4209

pethers requested a review from Copilot March 1, 2026 02:57

Copilot started reviewing on behalf of pethers March 1, 2026 02:58 View session

Copilot AI reviewed Mar 1, 2026

View reviewed changes

Merge branch 'main' into copilot/harden-egress-policies

80d176e

Copilot started work on behalf of pethers March 1, 2026 03:36 View session

Copilot finished work on behalf of pethers March 1, 2026 03:41

Merge branch 'main' into copilot/harden-egress-policies

6fc014b

pethers requested a review from Copilot March 1, 2026 10:48

Copilot started reviewing on behalf of pethers March 1, 2026 10:48 View session

Copilot AI reviewed Mar 1, 2026

View reviewed changes

Merge branch 'main' into copilot/harden-egress-policies

7e79308

Copilot started work on behalf of pethers March 1, 2026 12:40 View session

Copilot finished work on behalf of pethers March 1, 2026 12:44

Merge branch 'main' into copilot/harden-egress-policies

57bf1e6

pethers requested a review from Copilot March 1, 2026 13:06

Copilot started reviewing on behalf of pethers March 1, 2026 13:07 View session

Copilot AI reviewed Mar 1, 2026

View reviewed changes

Merge branch 'main' into copilot/harden-egress-policies

3beefe5

Copilot started work on behalf of pethers March 1, 2026 13:29 View session

Copilot finished work on behalf of pethers March 1, 2026 13:35

pethers requested a review from Copilot March 1, 2026 13:38

Copilot started reviewing on behalf of pethers March 1, 2026 13:38 View session

Copilot AI reviewed Mar 1, 2026

View reviewed changes

Merge branch 'main' into copilot/harden-egress-policies

35340a6

pethers marked this pull request as ready for review March 1, 2026 13:48

pethers approved these changes Mar 1, 2026

View reviewed changes

pethers merged commit 982000d into main Mar 1, 2026
11 checks passed

pethers deleted the copilot/harden-egress-policies branch March 1, 2026 13:56

Conversation

Copilot AI commented Mar 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes Made

Egress Policy Hardening

Allowlist Completeness

Dependency Pinning

Security Impact

Testing

🎯 Objective

📊 Current State

🚀 Desired State

🔧 Implementation Approach

🤖 Recommended Agent

✅ Acceptance Criteria

📚 References

🏷️ Labels

Comments on the Issue (you are @copilot in this section)

Uh oh!

github-actions bot commented Mar 1, 2026

🔍 Lighthouse Performance Audit

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

pethers commented Mar 1, 2026

Uh oh!

github-actions bot commented Mar 1, 2026

🔍 Lighthouse Performance Audit

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

pethers commented Mar 1, 2026

Uh oh!

github-actions bot commented Mar 1, 2026

🔍 Lighthouse Performance Audit

Uh oh!

Copilot AI commented Mar 1, 2026

Uh oh!

github-actions bot commented Mar 1, 2026

🔍 Lighthouse Performance Audit

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Mar 1, 2026 •

edited

Loading