Skip to content

Security: andreanjos/grokbot-headless

SECURITY.md

Security

Do not put OAuth tokens, daemon credentials, machine files, or full service logs in a public issue.

Report a security problem through GitHub private vulnerability reporting for this repository. If that option is unavailable, contact the repository owner through the private contact method shown on the GitHub profile.

Before you share logs, remove authorization headers, OAuth values, credential fields, machine IDs, email addresses, and local file contents.

The always policy permits remote commands without individual approval. Use it only on a host and account that you intend to expose to Grok Bot.

There aren't any published security advisories