Skip to content

add socket tier 1 reachability analysis - #48

Merged
tamirms merged 3 commits into
stellar:mainfrom
kanwalpreetd:main
Aug 28, 2026
Merged

add socket tier 1 reachability analysis#48
tamirms merged 3 commits into
stellar:mainfrom
kanwalpreetd:main

Conversation

@kanwalpreetd

Copy link
Copy Markdown
Contributor

Copilot AI review requested due to automatic review settings June 12, 2026 14:29

Copilot AI 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.

Pull request overview

Adds a scheduled GitHub Actions workflow to run Socket’s full-application reachability analysis for the friendbot repo, surfacing Tier 2 fallback situations as a non-failing warning while still failing the workflow on hard scan errors.

Changes:

  • Introduces a weekly + on-demand “Socket reachability scan” workflow.
  • Installs Go/Node tooling and runs socket scan create --reach with “continue-on-*” flags.
  • Parses scan logs to emit a GitHub Actions ::warning:: when Tier 1 reachability falls back to Tier 2.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/socket-scan.yml Outdated
Comment thread .github/workflows/socket-scan.yml Outdated
Comment thread .github/workflows/socket-scan.yml
kanwalpreetd and others added 2 commits June 29, 2026 02:32
- Drop the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 env block: every action here
  already declares `using: node24`, and runners have defaulted to Node 24
  since 2026-06-16 (Node 20 is removed 2026-09-16)
- Remove the unused Corepack step; corepack only shims yarn/pnpm, and this
  repo uses neither
- Read the Go version from go.mod (go 1.24.0) instead of hardcoding
  1.26.4, so the scan matches what this repo targets and cannot drift

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@tamirms
tamirms merged commit 4c0014e into stellar:main Aug 28, 2026
11 checks passed
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.

3 participants