MergeCost

Security & data

Your source code never leaves your CI. Only measurements do.

What leaves your CI

  • Per-request metrics: route templates, query fingerprints and counts, the project file and line a query came from, generated SQL text (unless redact_sql: true), HTTP hosts and counts, LLM model names and token counts, log and response byte sizes.
  • Static-scan findings: rule, file path and line number only — the code line itself stays in CI.
  • Your .mergecost.yml, the repository name, PR number and commit SHAs.

What never leaves

  • Source code, test data, request and response bodies.
  • Secrets and environment variables.

Production traffic SDK

Sends HTTP method, route template, request counts and response byte totals every five minutes. Never URLs, query strings, headers, bodies or personal data. It never raises errors into your request path.

GitHub App permissions

Read/write: contents, workflows, pull requests and Actions secrets, only on repositories you select. They are used to open the setup pull request and to write the MERGECOST_API_KEY secret. The workflow then posts comments with GitHub’s own short-lived GITHUB_TOKEN.

Never run the MergeCost workflow on pull_request_target: that would execute untrusted fork code with your secrets. The generated workflow uses pull_request and skips fork PRs.

API keys

CI and SDK keys are stored only as SHA-256 hashes and shown once. Revoke them any time on the repository page in the dashboard.

Infrastructure

  • API and dashboard on Google Cloud Run (us-central1); database on managed PostgreSQL (Supabase, US East).
  • All traffic over HTTPS. Client packages are served from a private, key-protected package index.
  • Payments by Dodo Payments as merchant of record; MergeCost never sees card details.

Report a vulnerability

Email support@jdtensor.com with “Security report” in the subject. Please give us reasonable time to fix an issue before disclosing it. See also the privacy policy.