HedgeDoc vs SiYuan

HedgeDoc's 1.x line ships every one to two months and is dominated by security response. Recent releases carry seven advisories between them — HTML injection via an email localpart, YAML frontmatter denial of service, CSRF in the Gist export, a rate-limit bypass through CF-Connecting-IP, a permission-value validation gap, missing upload security headers, and script execution in uploaded SVGs. Around those sit configuration knobs for the external-link warning, webp uploads, and rate limits.

Two threads run in parallel. The perimeter work reduces attack surface and maintenance burden at once: old API endpoints and unused config are deleted, Node 18 support is dropped now that its security window has closed, and features added in one release tend to gain an off switch in the next. The second thread is realtime correctness — concurrent-editing data loss, connections dropped mid-handshake, operations discarded during revision gap recovery — which is the only work aimed at the core editing experience rather than its edges.

Expect the 1.x line to continue as security and correctness maintenance, with more legacy endpoints and configuration removed rather than new editing features added.