Skip to content

Security: jjshay/intelligence-engine

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.0.x

Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability, please follow these steps:

How to Report

  1. Do NOT open a public GitHub issue for security vulnerabilities
  2. Email the maintainer directly with details of the vulnerability
  3. Include:
    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if any)

What to Expect

  • Initial Response: Within 48 hours
  • Status Update: Within 7 days
  • Resolution Timeline: Depends on severity
    • Critical: 24-48 hours
    • High: 7 days
    • Medium: 30 days
    • Low: 90 days

Security Best Practices for Users

  1. Keep dependencies updated: Run pip install --upgrade -r requirements.txt regularly
  2. Use virtual environments: Isolate project dependencies
  3. Protect API keys: Never commit AI provider API keys to version control
  4. Secure multiple API credentials: This system uses 5 AI providers - secure all keys
  5. Validate news sources: Be aware of potential misinformation in analyzed content
  6. Handle analysis results appropriately: AI analysis is not 100% accurate

Security Features

This project includes:

  • Dependabot: Automated security updates for dependencies
  • CodeQL: Static analysis for vulnerability detection
  • Pre-commit hooks: Security checks before commits (detect-private-key)
  • Environment variables: All API keys stored securely in .env files

AI API Security

  • Store API keys for all 5 AI providers (ChatGPT, Claude, Gemini, Grok, Perplexity) securely
  • Use separate API keys for development and production
  • Monitor API usage and set spending limits
  • Rotate API keys periodically

Acknowledgments

We appreciate responsible disclosure and will acknowledge security researchers who help improve this project's security.

There aren’t any published security advisories