// SECURITY

Security

You're trusting Bugbear with source code — often private. Here's how we handle it.

Sandboxed, ephemeral scans

Each scan runs against a fresh, isolated copy of your source that is discarded when the scan completes. Source code is not written to long-term storage; only the resulting findings and scan metadata are persisted.

Least-privilege access

Private-repo scanning uses the GitHub App with short-lived, per-installation tokens scoped to the repositories you choose. Tokens are used only for the scan and PR checks you request, and you can revoke the installation from GitHub at any time.

Secrets stay yours

When an agent finds a leaked credential, the report tells you where it is and how to rotate it — we don't copy the secret out or retain it. Findings store the location and remediation, not the raw secret material.

Safe live-surface probing

The optional deployed-URL probe is read-only and non-intrusive. It resolves and rejects private, loopback, link-local, and cloud-metadata addresses on every redirect hop, so it can't be pointed at internal infrastructure.

Payments & identity

Authentication is handled by Clerk and payments by Dodo Payments; Bugbear never stores passwords or card data.

Responsible disclosure

Found a vulnerability in Bugbear itself? We want to hear about it. Email support@bugbear.sh and we'll respond quickly. Please give us a reasonable window to fix issues before public disclosure.

We describe only controls that are actually in place today — no compliance badges we haven't earned.