Reporting a vulnerability

Mail security@wellworn.dev. Include the endpoint or the file, the steps to reproduce, and what an attacker gets out of it. You will get a reply within three working days and a fix timeline within seven.

In scope

The MCP server and every package in WellWorn-dev/wellworn, the hosted endpoint at https://mcp.wellworn.dev, the Claude Code plugin, and the skills.

Out of scope: the third-party registries and sites our importers read. A problem in npm, PyPI or GitHub belongs to them.

Please do not load test

The public tier is rate limited and abuse is blocked at the edge, so a load test proves nothing about the service and gets your address blocked. If you need to demonstrate a limit-bypass, describe the shape of it and we will reproduce it ourselves.

A wrong verdict is not a vulnerability

A verdict that recommends something you disagree with, or a trap that no longer applies, goes to the corpus process rather than to this address: open an issue or a pull request against the verdict file, or send submit_trap from inside your agent. The contributing page has both routes.

Our own reviews

The tree was read end to end on 8 September 2026: every route handler, server action, query and importer, with semgrep over the application and package code and a production dependency audit alongside the manual pass. Findings that were not fixed are written down with the reason rather than dropped. See server security for what that review covered.