All blog posts
Updates 2 min read

Commonveil 0.12.0: Security audit and built-in moderation

Commonveil 0.12.0 records security audit and built-in moderation. Here is the project history, technical detail and reasoning behind the update.

By Comutability Published Update from

Historical Commonveil release, 5 November 2026. Based on the project's official versioned release record. This does not establish an independent cryptographic audit.

Commonveil 0.12.0 records security audit and built-in moderation. Here is the project history, technical detail and reasoning behind the update.

Why this update matters

End-to-end encryption and sensible safety tools should coexist. Reports are intended for authorised moderators, not for unrestricted server access to private conversations. This release recorded permission fixes, protections against raids and floods, and workflows for reviewing reported behaviour. Moderation must still be governed by a clear policy and meaningful appeal routes.

What changed in version 0.12.0

The official release notes recorded the following changes. These describe the version at the time, and later releases may have replaced, improved or removed particular mechanisms.

  • Fixes from a full security review: channel permissions, private channels, call membership checks and safer word matching.
  • Reports to a server's moderators, encrypted to them alone, and escalation to the Commonveil team.
  • Numbered cases, warnings with automatic steps, flood and raid protection, staff limits, temporary bans and message purges.

How this fits the wider Commonveil direction

Comutability's wider aim is useful, accessible technology that gives people more control. For Commonveil that means encrypted communication, meaningful user permissions and the option to run a site independently. We also need to keep a clear boundary between what the project records as implemented, what has been tested and what still needs expert review.

The detailed release notes above provide a starting point for members and contributors to test the behaviour, read the documentation and challenge assumptions.

What to check next

Test staff access and escalation paths carefully, and keep the distinction between encrypted evidence and platform metadata visible.

Original sources

Sources and further reading

Explore the evidence and original project records behind this article.