add socket tier 1 reachability analysis#976
Conversation
There was a problem hiding this comment.
Pull request overview
Adds an automated GitHub Actions workflow to run Socket’s full-application reachability analysis for this repo on a weekly schedule (and on-demand), including logic to surface Tier 2 fallback as a non-failing GitHub Actions warning.
Changes:
- Introduces a new scheduled + manually-triggerable “Socket reachability scan” workflow.
- Installs Socket CLI and runs
socket scan create --reachwith “continue-on-*” reachability options. - Parses the scan log to emit a
::warning::annotation when Tier 2 fallback is detected.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - name: Install Socket CLI | ||
| run: npm install -g socket | ||
|
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b60d4e533b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| socket scan create --reach \ | ||
| --org=stellar \ |
There was a problem hiding this comment.
In this workflow context there is no checked-in Socket config, and Socket's scan create help says --repo/--branch are what associate the Scan with a dashboard repository/branch, otherwise they default to socket-default-repository/socket-default-branch (see https://docs.socket.dev/docs/socket-scan#repo--branch-names). As written, the scheduled js-stellar-base scan is uploaded under those generic defaults instead of this repository/default branch, so the repository's alerts/head scan in Socket will not be updated correctly (and can collide with other repos using the same defaults).
Useful? React with 👍 / 👎.
More info: https://stellarorg.atlassian.net/wiki/spaces/SCRT/pages/5689311233/Socket+Tier+1+Reachability+Analysis