Skip to content

Security: qiuxinyuan321/supppergrok

Security

SECURITY.md

Security policy

Secret handling

This repository must not contain:

  • API keys, OAuth tokens, cookies, passwords, private keys, or account exports;
  • local Grok/Codex configuration files;
  • session logs or raw production traces;
  • private hostnames, server addresses, or personal filesystem paths.

Run scripts/secret-scan.ps1 before every public push.

Reporting

Use GitHub's private security-advisory flow for suspected credential exposure. Do not paste live credentials into a public issue.

There aren't any published security advisories