Pretty Busy Solutions handles security reports through private, evidence-bound review.

Do not open public issues for suspected vulnerabilities. Send a concise report with reproduction context, affected repository, expected impact, and any relevant logs or commit hashes to the repository owner through an approved private channel.

No live customer data, credential material, production secrets, or unauthorized third-party systems should be used when reporting an issue. Proofs should be minimal, local where possible, and clearly separated from any destructive or externally mutating behavior.