Security

How to tell us about a vulnerability in Sailfork, and what to expect when you do.

Last updated

Reporting a vulnerability

Send what you found through the contact page at /contact?topic=security, or pick "Report a security issue" on the form. Security reports are marked and sent to a separate address when one is set. Please do not open a public issue, pull request or repository about it, and do not post details before we have had time to fix it.

The more of this you include, the faster we can act: the affected page, endpoint or command, the steps to reproduce it, what an attacker gains, and the version or time you saw it.

What is in scope

Sailfork itself: sailfork.com, its API, the git and SSH endpoints, the sailfork command line, the MCP server, caissons and CI runners. Problems in a third-party service we use belong with that service, unless Sailfork makes them worse.

Spam, abusive content and copyright claims are not vulnerabilities. Report those on the abuse page.

Testing in good faith

Test only against accounts and repositories you own. Do not read, change or delete other people’s data, do not degrade the service for other people, and stop as soon as you have shown the problem exists. Denial-of-service testing, social engineering of our people or users, and physical attacks are out of bounds.

What happens next

We read every report and reply to the address you give. We tell you when the problem is confirmed and when it is fixed, and credit you in the changelog if you want that.

This page has a machine-readable twin at /.well-known/security.txt, which points at the same form. We do not have a dedicated security email address yet.

Questions about this page go through the contact page. Fenil, who runs Sailfork, reads every message.

Loading Sailfork