Contact

Let's talk.

Questions about Cloakwave, feedback on a scan, or a vulnerability to report? Every message is read by a human.

✉️

Send an email

The fastest way to reach Cloakwave is by email. One address, one inbox, no ticketing system — messages go straight to a human.

info@cloakwave.io

What to include in your message

  • ✓ For general questions: describe what you're trying to do and what's blocking you. A short paragraph is plenty.
  • ✓ For feedback on a scan: include the finding title, the file name, and — if you can share it — the spec snippet that triggered the finding.
  • ✓ For false-positive reports: include the finding title and describe what your API actually does at runtime. That context is what turns a heuristic into a more accurate rule.
  • ✓ For vulnerability reports: include reproduction steps and, if relevant, a minimal spec or input that reproduces the issue. Please don't post it publicly or on social media.

Before you write

No. The scanner runs entirely in your browser. Your spec is parsed, analyzed, and scored locally — it is never uploaded, stored on a server, or transmitted anywhere. The only data that leaves your browser is the scan result saved to your own localStorage, and only if you scan more than once.
Possibly. The scanner uses deterministic rules against the OpenAPI spec, and some findings are heuristic — for example, a sequential ID pattern is flagged even if you enforce authorization elsewhere. If you report a false positive, include the finding title, the spec snippet that triggered it, and — if you can share it — what the actual runtime behavior is. That context helps turn the rule into something more accurate.
Not yet. The scanner, breach-precedent report, and threat model are free. If you want features that require a backend — team dashboards, persistent scan history, scheduled scans, CI gating — email and describe what you need. Real demand for those features is what determines what gets built next.
Email info@cloakwave.io with reproduction steps. Please don't post it publicly or open a public issue. Receipt will be acknowledged within 48 hours and a fix and disclosure timeline coordinated from there.