sbx/snyk-evo-ads-kit repository overview

⁠snyk-evo-ads

A Docker Sandboxes mixin (kind: mixin), requiring sbx 0.39.0 or later. The kit installs whichever Snyk components you request — AgentScan, Agent Guard, and/or Snyk Studio — directly from their public release channels. It stages optional corporate certificates, installs the requested components, and runs AgentScan at startup and after a 15-minute pause between attempts. There is no dependency on Snyk-internal infrastructure or any tenant-side configuration: what gets installed is exactly what you ask for.

⁠Getting started

Add the mixin to a built-in agent. With a local clone of this repo:

sbx run claude --kit ./snyk-evo-ads/

Or directly from the repo, without cloning:

sbx run claude --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=snyk-evo-ads"

If your network uses TLS interception, stage your corporate root certificate⁠ before creating the sandbox.

⁠Repository layout

snyk-evo-ads/
├── README.md
├── spec.yaml
└── files/home/
    ├── .snyk-kit/   # Component selection, auth, and download helpers
    └── corp-ca/     # Optional corporate root certificates

⁠Components

Select what to install with SNYK_COMPONENTS, a comma-separated list of scan, guard, and/or studio. It defaults to scan when omitted.

Scan and Guard are the same agent-scan binary (downloaded once, from github.com/snyk/agent-scan releases⁠, SHA-256 verified) and always live at ~/.local/share/snyk-agent-scan/agent-scan, in every mode. Studio is a separate binary from github.com/snyk/studio-recipes releases⁠, downloaded and verified the same way.

Credentials are supplied explicitly with -e. The kit does not declare credential defaults or import host variables. Install steps run unconditionally — the binaries are public and need no credential to install. Requesting scan or guard without its credential still installs the binary, but the corresponding hooks stay inactive (logged, not an error) until a credential is set and the sandbox is recreated.

⁠Default: free-tier AgentScan

sbx run claude \
  --kit ./snyk-evo-ads/ \
  --name "$(hostname)-sandbox-free" \
  -e SNYK_TOKEN

SNYK_COMPONENTS defaults to scan, so this installs AgentScan only.

⁠AgentScan + Agent Guard

sbx run claude \
  --kit ./snyk-evo-ads/ \
  --name "$(hostname)-sandbox" \
  -e SNYK_COMPONENTS=scan,guard \
  -e SNYK_ADS_PUSH_KEY

Guard hooks install directly, so the identity Guard reports matches Scan's — both use docker-sbx:${SANDBOX_NAME}:${SANDBOX_ID} — from the very first install.

⁠All three components

sbx run claude \
  --kit ./snyk-evo-ads/ \
  --name "$(hostname)-sandbox-all" \
  -e SNYK_COMPONENTS=scan,guard,studio \
  -e SNYK_ADS_PUSH_KEY

⁠Studio alone

sbx run claude \
  --kit ./snyk-evo-ads/ \
  --name "$(hostname)-sandbox-studio" \
  -e SNYK_COMPONENTS=studio

No credential is required to install Studio. Studio's Snyk CLI can instead authenticate interactively via snyk_auth/snyk auth inside the sandbox, or you can pass -e SNYK_TOKEN alongside SNYK_COMPONENTS=studio to pre-authenticate it. Never paste credentials into the agent conversation.

⁠Custom Snyk API base (SNYK_API)

By default Scan and Guard talk to https://api.snyk.io. Set SNYK_API to point them at a different Snyk API base instead — the kit passes it to guard install as --url, and to scan as --analysis-url with the same path AgentScan uses by default (only the host changes):

sbx run claude \
  --kit ./snyk-evo-ads/ \
  --name "$(hostname)-sandbox" \
  -e SNYK_COMPONENTS=scan,guard \
  -e SNYK_ADS_PUSH_KEY \
  -e SNYK_API=https://api.example-region.snyk.io

⁠Corporate certificates and network access

⁠Do you even need this?

Check what's actually terminating TLS on the way to Snyk's servers before assuming either way:

openssl s_client -connect downloads.snyk.io:443 </dev/null 2>/dev/null | grep -E '^\s*i:' | tail -1

A public CA in the output (DigiCert, Amazon, ISRG, etc.) means nothing is intercepting TLS — skip this section entirely. A corporate proxy name (Zscaler, Netskope, Palo Alto, ...) means your network is intercepting TLS and you need to stage its root certificate, below.

⁠Staging the corporate CA certificate

Place its PEM-encoded root certificate in files/home/corp-ca/ with a .crt extension — any filename works, the install step globs *.crt:

files/home/corp-ca/your-corporate-ca.crt

macOS, from the system keychain (replace "Zscaler Root CA" with your proxy's CA name):

security find-certificate -a -c "Zscaler Root CA" -p \
  /Library/Keychains/System.keychain \
  > files/home/corp-ca/your-corporate-ca.crt

Linux, from the system trust store (Debian/Ubuntu path shown; RHEL-based distros use /etc/pki/ca-trust/source/anchors/):

cp /usr/local/share/ca-certificates/your-corporate-ca.crt \
  files/home/corp-ca/your-corporate-ca.crt

From the live TLS chain, if you don't have keychain/trust-store access — this pulls the topmost certificate your proxy actually presents, which is usually an intermediate rather than a true self-signed root (proxies typically don't serve their root), but is sufficient as a trust anchor in practice:

openssl s_client -connect downloads.snyk.io:443 -showcerts </dev/null 2>/dev/null \
  | awk '/-----BEGIN CERTIFICATE-----/{buf=""} {buf=buf $0 "\n"} /-----END CERTIFICATE-----/{last=buf} END{printf "%s", last}' \
  > files/home/corp-ca/your-corporate-ca.crt

Validate before spending a sandbox create on it:

head -1 files/home/corp-ca/*.crt        # must read BEGIN CERTIFICATE
openssl x509 -in files/home/corp-ca/your-corporate-ca.crt -noout -text \
  | grep -A1 'Basic Constraints'                 # must read CA:TRUE

See the certificate guide⁠ for the full set of rules (PEM vs DER, root vs leaf, gitignore behavior). The kit adds certificates to the system trust store and sets Node's additional CA bundle. Missing certificates do not themselves abort setup, but intercepted downloads may fail without them.

⁠Network allowlist

The kit allows **.snyk.io (any host under snyk.io, any subdomain depth — covers api.snyk.io, deeproxy.snyk.io, downloads.snyk.io, and a custom SNYK_API host), plus registry.npmjs.org, github.com, and release-assets.githubusercontent.com. Snyk Code (SAST) needs access to deeproxy.snyk.io; AgentScan, Guard, and Studio binaries download from github.com/release-assets.githubusercontent.com. Organization policy may require these domains to be allowed centrally. Kit changes apply when creating a sandbox; existing sandboxes need their network policy updated or must be recreated.

⁠Agent-assisted security reviews

Inside the sandbox, ask the agent:

The kit's instructions explain authentication, binary discovery, and synchronous results via --show-analysis-results. AgentScan does not require snyk auth; Snyk CLI has separate authentication.

Background results are logged rather than inserted into an existing conversation. Enterprise background scans can submit asynchronous analysis to Snyk. MCP execution consent is preserved for interactive scans.

⁠Verification and troubleshooting

sbx kit validate ./snyk-evo-ads/
sbx exec "<sandbox-name>" sh -c 'sh "$HOME/.snyk-kit/resolve-components.sh"'
sbx exec "<sandbox-name>" sh -c 'cat "$HOME/.snyk/agent-scan-startup.log"'

Replace <sandbox-name> with the name passed at creation.

resolve-components.sh prints scan=0|1 guard=0|1 studio=0|1 auth_mode=enterprise|standalone|none and fails only if SNYK_COMPONENTS itself is malformed (an unknown component, or a value that resolves to none). AgentScan and Guard always share ~/.local/share/snyk-agent-scan/agent-scan; Studio's binary is at ~/.local/share/snyk-studio/snyk-studio-installer.