chore(security): Phase 0 hardening — headers, Semgrep CI, deps - #182
Merged
Conversation
✅ Deploy Preview for dev-bayanflow ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
ayoub3bidi
force-pushed
the
chore/phase-0-security-hardening
branch
from
June 21, 2026 13:02
22aa1bd to
478426c
Compare
35 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution workflow
develop: This PR targetsdevelop, notmain.Description
Phase 0 security hardening for Bayan Flow (no Supabase/auth work). Adds Netlify HTTP security headers and CSP, wires Semgrep into CI via
SEMGREP_APP_TOKEN, tightens GitHub Actions with production dependency auditing and safer fork PR deploy behavior, bumps vulnerable dependencies, and alignsSECURITY.mdwith reality. Socket continues to run via the org GitHub App (no duplicate CLI workflow).Type of Change
Related Issues
Fixes #
Changes Made
X-Frame-Options,Referrer-Policy,Permissions-Policy; alignNODE_VERSIONto24.11.1SEMGREP_APP_TOKENpnpm audit --prod --audit-level high; skip Actions Netlify deploy for fork PRsreact-router-dom(≥7.12),vitest(≥3.2.6),playwright(≥1.55.1)Algorithm Details (if applicable)
N/A — no algorithm changes.
Testing
pnpm test:run)Test Results
CI / PR checks (PR #182)
Code Quality,Unit Tests,Build,All Checks PassedSemgrepSocket Security: Pull Request AlertsHeader rules - dev-bayanflow— passManual verification (recommended for reviewers)
All Checks PassedScreenshots/GIFs
N/A — infrastructure and security configuration only; no UI changes.
Code Quality
pnpm lint)pnpm format:check)Performance Impact
CSP and security headers add negligible runtime overhead.
Accessibility
N/A — no UI changes.
Breaking Changes
Checklist
Additional Notes
GitHub settings (applied via
gh, outside this PR diff)mainrequired checks:Code Quality,Unit Tests,Build,All Checks Passed,Socket Security: Pull Request Alerts,Semgrep(removed staleUnit Tests (20.x))main: 1 required approving reviewBranch Protection - develop(0 reviews) ·Branch Protection - main(1 review); both include non-fast-forwardallow_force_pushes: true;non_fast_forwardruleset onmainblocks force pushes in practiceManual dashboard follow-up (post-merge)
Socket org → Security Policy: set critical supply-chain alert types to Block
Semgrep Cloud: confirm project linked; enable
p/javascript,p/react,p/owasp-top-ten; Block on hardcoded secretsBranch:
chore/phase-0-security-hardening(fromdevelop)PR: chore(security): Phase 0 hardening — headers, Semgrep CI, deps #182
Reviewer Guidelines: