Skip to content

Security: emavit/Planora

Security

SECURITY.md

Security

Do not post secrets, private projects or exploit-bearing files in public issues. Use GitHub private vulnerability reporting if enabled. Until that is configured, contact the repository owner privately rather than publishing sensitive reports. No dedicated security email has been configured in this source snapshot.

Describe the affected version, impact and a minimal synthetic reproduction. Do not attach real credentials or confidential schedules. Recovery files can contain complete project data and source-path provenance. AI/MCP connections can send explicitly reviewed content to external services.

Only a Windows preview is currently qualified to the limits in docs/RELEASE.md. Updates and response timelines are best-effort; no security support SLA is implied.

There aren't any published security advisories