Skip to content

Security: xscriptordev/xfetch

SECURITY.md

Security Policy

Reporting Security Vulnerabilities

If you discover a security vulnerability in xfetch, please report it responsibly by contacting:

Email: x@xscriptor.com

What to Include

When reporting a security issue, please provide:

  1. Description — A clear explanation of the vulnerability
  2. Type — What kind of security issue is it? (e.g., buffer overflow, injection, privilege escalation, etc.)
  3. Steps to Reproduce — Detailed steps to trigger the vulnerability
  4. Impact — How severe is the issue? What could an attacker do?
  5. Affected Versions — Which versions of xfetch are affected?
  6. Proposed Fix (optional) — If you have a suggestion for how to fix it

Guidelines

  • Do not open public GitHub issues for security vulnerabilities
  • Do not disclose the vulnerability publicly until a fix is released
  • Do give the maintainers reasonable time to address the issue before public disclosure
  • Typically, we aim to respond within 7 days and release a fix within 30 days for critical issues

Security Best Practices for Users

While xfetch is designed to be safe, keep these recommendations in mind:

  1. Keep updated — Always use the latest version of xfetch
  2. Verify downloads — Check checksums when downloading binaries
  3. Configuration privacy — Be careful when sharing custom configs that may contain sensitive paths
  4. Network features — If using IP detection features, be aware of potential privacy implications
  5. Third-party plugins — Only use plugins from trusted sources if the plugin system is enabled

Supported Versions

Version Status Support Until
latest Active latest

Security Updates

Security fixes will be released as soon as possible. Critical vulnerabilities will receive priority treatment.


Thank you for helping keep xfetch secure!

There aren’t any published security advisories