Vulnerability Disclosure Policy

We build a tool that finds vulnerabilities, so we want to hear about ours. If you find a security issue in Elliot, report it to us and give us a chance to fix it before you share it.

Report a vulnerability

Email nick@divergentlabs.xyz with “Security report” in the subject. Include:

  • the affected host, page, or API endpoint;
  • the steps to reproduce the issue, with any proof-of-concept code, requests, or screenshots;
  • the impact you think it has;
  • whether you want to be credited, and under what name.

The same address takes reports of Elliot being used to test systems without the owner’s authorization.

Our security.txt lists this contact in machine-readable form.

Scope

In scope:

  • tryelliot.app and its subdomains, including the dashboard at dashboard.tryelliot.app;
  • elliot.divergentlabs.xyz and api.elliot.divergentlabs.xyz;
  • the Elliot GitHub App;
  • the Elliot MCP server;
  • the sandboxes Elliot runs proofs of concept in, including escape from a sandbox to our infrastructure.

Out of scope:

  • services we use but do not run, such as GitHub, Stripe, and Vercel (report those to the provider);
  • denial of service, load testing, and volume-based attacks;
  • social engineering of our staff or users, and physical attacks;
  • reports from automated tools without a demonstrated impact;
  • missing security headers, cookie flags, or email authentication records (SPF, DKIM, DMARC) without a demonstrated impact;
  • clickjacking on pages without sensitive actions, self-XSS, and logout CSRF;
  • vulnerabilities that require a compromised device or browser.

Rules for testing

  • Test only against Accounts and workspaces you created. Use a repository you own when you run scans.
  • Access only the data you need to show the issue. If you reach another user’s data, stop, do not keep or share it, and tell us in your report.
  • Do not degrade the Services for other users, and do not alter or delete data that is not yours.
  • Do not use Elliot to test systems you are not authorized to test (Terms, Section 2.7).
  • Keep the details private until we have fixed the issue, or until 90 days after your report, whichever comes first. If we need more time, we will tell you why and agree a date with you.

Safe harbor

When you research and report in good faith under this policy, we consider your work authorized under Section 2.2(d) of our Terms of Use. We will not pursue or support legal action against you for it, and if a third party takes legal action against you over it, we will make clear that you acted under this policy. If you are unsure whether something you plan to do fits this policy, ask us first.

What you can expect from us

  • We confirm we received your report within 3 business days.
  • We tell you whether we can reproduce the issue and keep you updated until it is fixed.
  • We tell you when the fix is live, and credit you by name if you want, once the issue is public.

This program offers public credit, not cash rewards.