Skip to content

Security: ryanxwy/AutoBroker-Python

Security

docs/SECURITY.md

Security Policy

AutoBroker is a local-first tool that can read Gmail, parse dealer replies, and prepare dealer-visible actions. Treat security issues seriously when they affect tokens, local data, approval gates, browser automation, or outbound messages.

Report A Vulnerability

Use GitHub private vulnerability reporting if it is enabled for this repository. If it is not available, open a minimal GitHub issue with [Security] in the title and do not include secrets, OAuth tokens, private emails, screenshots with personal data, or exploit details.

Include:

  • A short description of the affected surface.
  • The version or commit.
  • Reproduction steps using fake data whenever possible.
  • Whether the issue can bypass an approval gate, expose local data, or perform a dealer-visible action.

Sensitive Surfaces

  • Gmail OAuth tokens stored through macOS Keychain.
  • ~/.autobroker/autobroker.db and ~/.autobroker/logs/.
  • Dealer emails, attachments, quotes, and extracted quote records.
  • Browser MCP sessions used for dealer discovery and form workflows.
  • Approval gates for outbound Gmail sends and dealer form submissions.

Approval-Gate Security Boundary

These actions must require explicit human approval:

  • Sending outbound Gmail.
  • Submitting a dealer website form.
  • Running irreversible suppression/demotion writes in dealer_hygiene.
  • Confirming pipeline_reset with a typed YES.

Report any bypass, silent auto-approval, or misleading approval prompt as a security issue.

Secret Handling

Do not commit:

  • .env
  • Gmail OAuth client secrets or refresh tokens
  • local SQLite databases
  • live harness evidence
  • browser MCP screenshots or snapshots containing personal data

The repository ignores the normal local paths for those files. If a secret is committed by mistake, revoke or rotate it before removing it from git.

There aren't any published security advisories