Skip to content

Security: SiteQ8/PublicEye

SECURITY.md

Security Policy

Reporting Vulnerabilities

  1. Do not open a public GitHub issue.
  2. Email Site@hotmail.com with subject: [PublicEye Security] Brief description
  3. Include steps to reproduce and potential impact.

Response: Acknowledgment 48h, status 7d, resolution 30d.

Scope

In scope: Code injection, data leakage, credential exposure in reports, dependency vulnerabilities. Out of scope: Target website vulnerabilities, third-party API issues.

Responsible Use

PublicEye is for authorized security assessments only. Users are responsible for obtaining proper authorization before scanning any target.

There aren’t any published security advisories