Skip to content

Security: StanleyMasinde/twitter

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
latest

Reporting a Vulnerability

We take the security of Twitter CLI seriously. If you believe you've found a security vulnerability, please follow these steps:

  1. Do NOT disclose the vulnerability publicly (no GitHub issues, forums posts, social media, etc.).
  2. Email the details to: security@stanleymasinde.com
    • Include a detailed description of the vulnerability
    • Steps to reproduce the issue
    • Potential impact
    • Any suggestions for remediation

What to Expect

  • Acknowledgment: We'll acknowledge your email within 48 hours.
  • Verification: Our team will verify the vulnerability and determine its impact.
  • Fix Development: If confirmed, we'll develop a fix.
  • Public Disclosure: Vulnerabilities will only be disclosed publicly after a fix has been released.

Security Best Practices

When using Twitter CLI:

  1. Keep your tokens secure: Never share your Twitter API credentials.
  2. Update regularly: Always use the latest version of the CLI.
  3. Review permissions: Ensure your Twitter app has only the permissions it needs.

Dependencies

This project depends on various third-party libraries. We strive to:

  1. Keep dependencies up-to-date
  2. Monitor security advisories for dependencies
  3. Address security issues promptly

Thank you for helping keep Twitter CLI secure!

There aren’t any published security advisories