Wings is under active development. Security fixes are applied to the default branch (master) and included in the next deployment to wings.nopejs.me.
| Version | Supported |
|---|---|
master (latest) |
Yes |
| Older commits / forks | Best effort |
Please do not report security vulnerabilities through public GitHub issues.
If you believe you have found a security issue in Wings:
- Email or DM the maintainer via GitHub (Sabique-Islam) with details, or use GitHub's private vulnerability reporting if enabled.
- Include:
- Description of the vulnerability and potential impact
- Steps to reproduce (proof of concept if possible)
- Affected URLs, components, or files if known
- Your environment (browser, OS) if relevant
- Allow reasonable time for investigation and remediation before public disclosure.
We aim to acknowledge reports within 72 hours and provide a status update within 7 days.
Examples of in-scope issues:
- Authentication or session bypass
- Row Level Security (RLS) bypass exposing other users' entries
- Share token or collaboration permission escalation
- Server-side request forgery (SSRF) in edge functions
- Cross-site scripting (XSS) with realistic exploit path
- Injection in Supabase RPCs or edge functions
- Exposure of service-role keys or secrets in client bundles or public repos
- Data loss or corruption vulnerabilities in save/load paths
- Missing security headers on third-party hosts outside project control
- Social engineering attacks
- Denial of service without demonstrated impact on user data
- Issues requiring physical access to a user's device
- Vulnerabilities in dependencies with no practical exploit in Wings (still welcome as low-severity reports)
We support good-faith security research. Do not:
- Access, modify, or delete data belonging to other users
- Disrupt production services (wings.nopejs.me, Supabase, collab hosts)
- Send spam or phishing through any Wings email or auth flows
Testing should use your own Supabase project and local/dev environments when possible.
- Never commit
.env, API keys, service-role keys, or OAuth secrets. - Client env vars must use the
VITE_prefix only for public Supabase anon keys and URLs. - Server secrets belong in Supabase edge function secrets or collab server env — see LOCAL_SETUP.md and .env.example.
If you accidentally commit a secret, rotate it immediately and notify the maintainer.
If users report missing or blank journal content (not traditional CVE-style bugs), treat as urgent:
- Do not ask users to retry saves that might overwrite content.
- Follow the internal runbook: wings-incident-response skill
- Use the Data loss / missing content issue template for tracking.
These incidents may overlap with security but are handled with recovery-first procedures.
We appreciate responsible disclosure. With your permission, we will acknowledge researchers in release notes or security advisories.