Resources

Security.

How to report a vulnerability, and where it goes

If you've found a security problem in something Considus makes, I'd like to hear about it, privately, and before anyone else does. Please don't open a public issue or a pull request.

How to report it

Email security@considus.com, whatever it's about. If email isn't an option for you, the support form reaches me too.

If you'd rather keep it on GitHub, you can use GitHub's private reporting for one of the open-source projects instead. It's the Report a vulnerability button on the project's Security tab, for Proton Bridge MCP, PageSpeed Insights MCP or any of the Catchlight repositories. GitHub asks you to sign in first, and only you and I can see the report.

Tell me what you found, how to reproduce it, which version, commit or page it affects, and what it lets an attacker do. A proof of concept helps, but a clear description is plenty.

What happens next

I'll acknowledge your report within 3 business days and keep you posted while I look into it.

This is coordinated disclosure, so please give me a reasonable amount of time to ship a fix before you make it public. You're welcome to the credit once it's out, or to stay anonymous, whichever you'd prefer.

The same terms cover every Considus project and both websites, catchlight.app and considus.com.

Safe harbour

You won't face legal action from me or from Considus for research done in good faith, so long as you avoid violating anyone's privacy, avoid destroying data, and follow this policy.

This website's terms allow you to probe its security as part of good-faith research.

This website

For a problem on considus.com, tell me which page it affects. That includes the code that runs on its server, such as the mailing-list sign-up and the support form. Its code isn't public, so GitHub's private reporting isn't an option for it.

The reporting address is also in this website's security.txt, the file security tools look for.

What's out of scope

Services I don't control are out, because those aren't mine to fix. That means Cloudflare's own platform, which hosts the site, and EmailOctopus, which runs the mailing list.

The same goes for the reports an automated scan turns up: a missing security header, missing or weak SPF, DKIM and DMARC records, clickjacking on a page with nothing sensitive to click, and best-practice advice with no demonstrated impact. Social engineering and denial of service are out too.

Proton Bridge MCP and PageSpeed Insights MCP

What counts as in scope is different for each of these two open-source servers, so it's spelt out in the Proton Bridge MCP policy and the PageSpeed Insights MCP policy. Bugs in Proton Mail Bridge itself belong with Proton, and the behaviour of Google's APIs is out of scope for PageSpeed Insights MCP.

Both have one line of development, on the main branch. Fixes land there, and there are no separately maintained older releases to back-port them to.

Catchlight

Catchlight has its own policy, at catchlight.app/security, covering the apps, their open-source code and the catchlight.app website. It works to the same terms as this page.