Skip to content

TEST ONLY: run Socket reachability against ynab-sast-scanner#8 - #117

Draft
sgrammargs wants to merge 1 commit into
add-socket-reachabilityfrom
test-socket-reachability-followups
Draft

sgrammargs wants to merge 1 commit into
add-socket-reachabilityfrom
test-socket-reachability-followups

Conversation

@sgrammargs

@sgrammargs sgrammargs commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

TEST ONLY: do not merge. This exists to run ynab/ynab-sast-scanner#8 from a downstream repo before it merges. Close it, and delete the branch, once the run is checked.

It's based on #114's branch, so the diff is only the test change. The wrapper points at #8's branch (fix-socket-reachability-followups) instead of @main, and also triggers on pushes to this branch. Pushing this branch starts the run.

ynab-sdk-ruby is the "clean repo" case from #8's QA plan: its last test run had no fallbacks. What to check:

  • The job passes. Before Invalid Account Types #8, the fallback parser failed the step whenever nothing fell back.
  • No "Socket reachability fallback" warnings on the run.
  • The log shows CLI v1.8.2.
  • The scan is created, tagged with this branch, with the "not the default branch" notice.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sgrammargs

Copy link
Copy Markdown
Contributor Author

Reachability scan successfully uploaded to Socket: https://socket.dev/dashboard/org/ynab/sbom/f629b235-e2fd-4f39-b5be-7bebfca466c4

0 findings is correct - not an error.

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.

1 participant