Visual Leak Checker handles sensitive support artifacts by design. Do not include real screenshots, PDFs, account identifiers, phone numbers, faces, QR codes, or private incident details in public issues.
Report security issues privately to the maintainers. Use synthetic examples when describing a problem.
This prototype is not an emergency response channel. Do not use public issues for active incidents, time-sensitive safety requests, account recovery emergencies, legal requests, provider coordination, or real-world threat reporting. Public reports must use synthetic reproduction steps and should never include sensitive operational details.
Do not post real account inventories, phone numbers, private keys, incident logs, screenshots, victim data, live phishing URLs, DNS targets, origin IPs, provider tickets, private user exports, operational infrastructure details, or private contacts in public issues, pull requests, discussions, release notes, or demo artifacts. Use synthetic reproduction steps and ask for a private reporting path when sensitive details are needed.
This prototype accepts synthetic or manually redacted observation JSON. It should not be treated as proof that an artifact is safe to publish.
- biometric identification
- forensic image authenticity
- malware detection
- complete anonymization guarantees
Before public release or grant-review packaging, run these from the portfolio root:
npm run readiness
npm run frontend:capability-map
npm run cli:entrypoints
npm run number:local-first
npm run docs:advisory-safety
npm run safety:contracts-inventory
npm run supply-chain:safety
npm run metadata:boundary
npm run verify