Skip to content

Security: vankudothuadhinaik/RepoPilot

Security

SECURITY.md

Security Policy

Supported versions

Security fixes target the latest released version on the default branch.

Reporting a vulnerability

Do not publish exploit details in a public issue. Contact the repository owner privately through GitHub's security advisory feature if enabled, or request a private reporting channel before sharing sensitive details.

Current security boundaries

  • Local-first, read-only repository indexing.
  • Common secret files, generated folders, binaries, symlinks, and oversized files are excluded by default.
  • Repository text is treated as data, not trusted instructions.
  • This MVP does not execute shell commands or apply code patches.
  • The /api/* routes require a shared bearer token via REP_PILOT_API_TOKEN; the CLI refuses non-loopback binds unless the token is configured. Docker startup requires the token and Compose binds the published port to host loopback.
  • The token is a single shared secret, not user identity, role-based authorization, or tenant isolation. Rate limiting, TLS, and a reviewed hosted deployment design remain outstanding.

Limitations

These controls are defense-in-depth, not a security certification. Review the threat model and run security tests before processing sensitive repositories.

There aren't any published security advisories