Skip to content

Security: arnabk/agentgrove

Security

docs/SECURITY.md

Security policy

Reporting

Do not open public issues for security problems.

Email security@agentgrove.dev (placeholder; update before public launch). GPG key will be published before public launch.

We aim to acknowledge within 72 hours and provide a remediation timeline within 7 days.

Scope

  • The Rust backend binary agentgrove-server.
  • The built static frontend served by the binary.
  • Default configuration shipped with releases.

Out of scope:

  • User-installed agent CLIs (Claude, Codex, Kimi, etc.).
  • User-provided OS shells for pre/post scripts.

Defaults

  • Bind: 127.0.0.1 only.
  • No built-in authentication. The server trusts whoever can reach the loopback socket. Do not expose the port to other hosts without an external auth proxy.
  • Remote bind (AGENTGROVE_BIND=0.0.0.0) is allowed but the server logs a warning. Front it with a reverse proxy that adds auth/TLS.
  • Provider API keys are stored in the OS keyring (keyring crate), never in the database.

There aren't any published security advisories