Skip to content

root - chore: defense - wrap installs with Socket Firewall - #70

Merged
jaredwray merged 2 commits into
mainfrom
cursor/defense-actions-socket-firewall-64a2
Sep 9, 2026
Merged

jaredwray merged 2 commits into
mainfrom
cursor/defense-actions-socket-firewall-64a2

Conversation

@jaredwray

@jaredwray jaredwray commented Sep 9, 2026 •

Copy link
Copy Markdown
Contributor

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines and Code of Conduct
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
CI / supply-chain hardening.

Summary

Installs Socket Firewall Free on every job and wraps pnpm install with sfw (defense-in-depth § 4).

Status update

DEFENSE_IN_DEPTH.md: Socket Firewall → (PR #70 pending); Actions SHA pins → PR #69

Changes

Verification

  • Every job with steps: has the Firewall step
  • No remaining unprefixed pnpm install / npm install in workflows
  • npx actions-up -y --style sha reports SocketDev/action up to date
  • CI on this PR: tests (build-test 22/24/26), code-coverage (build), CodeQL

Reference

defense-in-depth-nodejs § 4

Open in Web Open in Cursor 

cursoragent and others added 2 commits September 9, 2026 20:27
Install SHA-pinned SocketDev/action after checkout on every job and
run sfw pnpm install --frozen-lockfile. Reconcile Actions SHA pins
as merged in PR #69.

Co-authored-by: Jared Wray <me@jaredwray.com>
Co-authored-by: Jared Wray <me@jaredwray.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the security documentation in DEFENSE_IN_DEPTH.md and SECURITY.md to reflect that GitHub Actions are now pinned to full commit SHAs. The reviewer suggested marking the Socket Firewall integration checklist item as completed rather than pending, since this pull request implements that integration.

Comment thread DEFENSE_IN_DEPTH.md
- [ ] Every action pinned to a full commit SHA (`npx actions-up`) (PR #69 pending)
- [ ] Every job installs Socket Firewall (`SocketDev/action` SHA-pinned, `firewall-version` pinned); `pnpm install` / `npm install` run as `sfw pnpm install` / `sfw npm install`
- [x] Every action pinned to a full commit SHA (`npx actions-up`) — PR #69
- [ ] Every job installs Socket Firewall (`SocketDev/action` SHA-pinned, `firewall-version` pinned); `pnpm install` / `npm install` run as `sfw pnpm install` / `sfw npm install` (PR #70 pending)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Since this pull request implements the Socket Firewall integration (as described in the PR title and summary), this checklist item should be marked as completed ([x]) and the (PR pending) suffix should be removed.

Suggested change
- [ ] Every job installs Socket Firewall (`SocketDev/action` SHA-pinned, `firewall-version` pinned); `pnpm install` / `npm install` run as `sfw pnpm install` / `sfw npm install` (PR #70 pending)
- [x] Every job installs Socket Firewall (`SocketDev/action` SHA-pinned, `firewall-version` pinned); `pnpm install` / `npm install` run as `sfw pnpm install` / `sfw npm install`

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Leaving this unchecked with (PR #70 pending) on purpose. security-status-tracking only flips an item to - [x] … — PR #n after that PR merges. Checking it off here would claim Socket Firewall is on main before it is.

@jaredwray
jaredwray marked this pull request as ready for review September 9, 2026 20:29
@cursor

cursor Bot commented Sep 9, 2026

Copy link
Copy Markdown

Gemini suggested checking off the Socket Firewall item in this PR. I left it as (PR #70 pending) until merge; no code change from that review.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 9, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-09T20:33:04.899673Z 6740b6b Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codecov

codecov Bot commented Sep 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (ba2b132) to head (6740b6b).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #70   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           19        19           
  Branches         1         1           
=========================================
  Hits            19        19           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jaredwray
jaredwray merged commit 389503a into main Sep 9, 2026
10 checks passed
@jaredwray
jaredwray deleted the cursor/defense-actions-socket-firewall-64a2 branch September 9, 2026 21:18
jaredwray added a commit that referenced this pull request Sep 9, 2026
* ci: lint GitHub Actions workflows with zizmor

Add check-workflows.yaml so every PR runs zizmor with Socket Firewall
in front. Reconcile Socket Firewall as merged in PR #70.

Co-authored-by: Jared Wray <me@jaredwray.com>

* chore: record PR #71 on the zizmor checklist item

Co-authored-by: Jared Wray <me@jaredwray.com>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants