Contributing

June 18, 2026 · View on GitHub

PRs welcome! Guidelines:

Adding Dorks/Queries

  • Use the KEYWORD convention (mandatory, since v1.3.0). Secret-seeking value strings must be a "KEYWORD" placeholder, or the query must carry a native scope filter (org:, site:, hostname:, net:). Service fingerprints (titles, paths, ports, env-var names, key prefixes) stay as-is.
    • ✅ site:grok.com/share "KEYWORD" · "OPENAI_API_KEY" path:*.env org:YOUR_ORG
    • ❌ site:grok.com/share "password" (unscoped credential dragnet — will be closed)
  • Verify it works before submitting; state the date and engine.
  • Include status indicator: 🟢 Active / 🟡 Degraded / 🔴 Dead
  • Place in the correct file under dorks/
  • Use modern GitHub Code Search syntax (path: not filename:)

Adding Tools

  • Must be AI/ML-specific — no generic OSINT tools
  • Verify the repo exists and is actively maintained
  • Include: name, description, maintainer, link

Threat Intelligence

  • Include dates, sources, and verifiable references
  • Map to MITRE ATT&CK where applicable

Detection Rules

  • Follow Sigma format
  • Include falsepositives section

Process

  1. Fork → 2. Branch → 3. Commit → 4. PR with description

Rules

  • No active credentials, real API keys, or PII
  • Authorized testing and legitimate research only
  • Responsible disclosure

Contact: septimus@7waysecurity.co