Nullgap.dev Docs

Security and privacy

Reporting a vulnerability

How to tell Nullgap privately about a security problem in the service, what to include, and what happens after you report it.

If you think you have found a security problem in Nullgap (the console, the API, the MCP endpoint, the command line tool or the client skill pack), please tell us privately first. We would rather hear about it early, and a private report gives us the chance to fix it before anyone else can use it.

#How to report

E-mail security@nullgap.dev. The same address is published in the machine-readable file at /.well-known/security.txt on every Nullgap server.

Please do not report security problems in a public issue, a forum post or a support thread that other people can read. If you are a customer, you can also tell us through your usual support channel, but say that it is a security report so it reaches the right people.

#What to include

The more of this you can give, the faster we can understand and fix the problem:

  • what the problem is and what someone could do with it;
  • the address, page, API route or command it affects;
  • the steps to reproduce it, as short as you can make them;
  • what you expected to happen and what happened instead;
  • any request ids shown in error messages (they start with req_);
  • whether you think anyone else is already using the problem.

Please do not include real secrets, other people's personal data or large amounts of data taken from a workspace. A short excerpt that shows the problem is enough.

#Testing in good faith

When you look for problems:

  • only test with workspaces and accounts that are your own, or that you have permission to use;
  • stop as soon as you can show the problem, and do not read, change or delete other people's data;
  • do not run tests that degrade the service for others (load tests, denial of service, spam);
  • give us a reasonable time to fix the problem before you tell anyone else about it.

We will not take action against anyone who reports a problem to us in good faith and follows these points.

#What happens next

We intend to acknowledge your report within three working days, and to keep you informed while we look into it. This is what we aim for, not a guarantee: a complex report can take longer to understand.

Once we have confirmed the problem we work on a fix and tell you when it is out. If you would like to be named when the fix is announced, say so in your report; if you prefer to stay anonymous, we respect that.

Nullgap documentation