Catch a vulnerability report before it becomes a normal bug

A researcher reporting a hole in the product reaches you, and the details stay off a public issue.

When the next email arrives

A researcher writing "your reset token does not expire" should not hit the bug rule, get an apology, and land in a public Linear issue. The phrase is specific so AI can prefer it over "Bug report".

The security-questionnaire rule is the other neighbor: SOC 2 packs and DPAs. This one is someone telling you something is broken in a way you would not want quoted.

How to add this rule

  1. Paste the phrase. If you already have a bug phrase, keep the words "vulnerability" and "researcher" here so AI can split them.
  2. Tag Security, assign the founder, notify, and add the note.
  3. Send a fake bounty email and a fake "the button is broken" email. They should take different rules.

While you set this up

The whole library

Also in Alerts