Team setup

Setup intake

Use this checklist after purchasing the Team Setup package. Share enough context to configure the scanner, but keep credentials and raw private MCP config values out of email.

Email setup intake Back to pricing

Send

Purchase email, repository URL or host, CI provider, MCP config paths, preferred branch, and whether SARIF upload is available.

Include a redacted MCP config snippet with commands, args, package names, URLs, and broad paths preserved where possible.

Do not send

Do not send secrets, API tokens, OAuth refresh tokens, private keys, raw `.env` files, full customer data, or production-only credentials.

Replace credential values with placeholders such as `REDACTED_GITHUB_TOKEN` before sharing.

Redacted MCP config

{
  "env": {
    "GITHUB_TOKEN": "REDACTED_GITHUB_TOKEN"
  },
  "args": ["--repo", "owner/private-repo"]
}

Delivery target

The setup package targets one repository and includes CLI wiring, GitHub Action configuration, policy and baseline review, SARIF or PR comment setup, and an audit pack closeout.

Support continues through the email used at checkout unless another contact is explicitly provided.