Connect Socket to GitHub Copilot
Give GitHub Copilot governed access to Socket’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Socket to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Socket in Runlayer
Add Socket from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
Install the Runlayer CLI so GitHub Copilot can reach Socket, which runs on the user’s machine.
GitHub Copilot setup guide - 3
Sign in to Socket
An admin adds Socket credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Socket from GitHub Copilot
Socket’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
1 Socket tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call. 1 read data only.
Depscore
Query dependency security scores across npm, PyPI, cargo, and other package ecosystems.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Socket call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more