Skip to content

Add Socket Firewall (free) to shared setup + test workflow #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
oxyc wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Add Socket Firewall (free) to shared setup + test workflow #18

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3ba9b19
Add Socket Firewall (free) to shared setup + test workflow
oxyc May 13, 2026
85941f1
Move SocketDev/action to workflow level
oxyc May 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions .github/workflows/test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,25 @@ jobs:
packagist_github_token: ${{ secrets.PACKAGIST_GITHUB_TOKEN }}
yoast_license_token: ${{ secrets.YOAST_LICENSE_TOKEN }}

- name: Install Socket Firewall
# Free edition — no token required. Installs `sfw` on PATH for this job.
# Placed here rather than in the setup composite because PATH additions
# made by Node actions inside composite actions do not reliably
# propagate to subsequent workflow-level steps.
uses: SocketDev/action@ba6de6cc0565af1f42295590380973573297e31f # v1.3.2
with:
mode: firewall-free

- name: Install npm packages through Socket Firewall
# Pre-install via `sfw` so Socket can block known-malicious packages
# before they hit disk. The subsequent `npm install` invoked by the
# composer build script becomes a no-op against this populated cache,
# except for any net-new packages it pulls — those are the residual
# gap. Per-project composer scripts can close the gap by switching
# their own `npm install` to `sfw npm install`.
if: hashFiles('package-lock.json') != ''
run: sfw npm ci --ignore-scripts

- name: Install development packages
run: composer install:development

Expand Down