Route CI gem installs through Socket Firewall registry#33
Merged
Conversation
Mirrors rubygems.org through the Socket Firewall registry so CI gem installs are scanned for supply-chain risk before fetch. Auth is injected at runtime via the socket-firewall CircleCI context — no credential committed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tomasdeane-intercom
approved these changes
Jun 10, 2026
eakashsaini
approved these changes
Jun 10, 2026
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
3 participants
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.
Why?
Part of a CI supply-chain hardening effort: dependency installs should be scanned by Socket Firewall before they're fetched. This repo's CI installed gems directly from rubygems.org with no such scanning.
How?
Mirrors rubygems.org through the Socket Firewall registry before
bundle install, with the registry token injected at runtime via thesocket-firewallCircleCI context — no credential committed — plus a verify step that fails the build if the mirror isn't active.Generated with Claude Code