Mermaiden
Let the machine draw. Keep the meaning.
Software can generate a diagram in an instant. The harder problem is knowing whether that diagram still means what you intended after an agent, tool, or application changes it.
Mermaiden turns diagrams into typed, discoverable state. It validates semantic commands, can apply related changes atomically, preserves versioned snapshots, and renders deterministic Mermaid source—so automation can move quickly without turning meaning into guesswork.
The package produces Mermaid text rather than owning its presentation. Render that text in a Markdown viewer, a browser, or your own Mermaid CLI workflow.
Documentation
- Documentation entrance
- Tutorials
- How-to guides
- Explanation
- Architecture and ownership
- Glossary
- Technical reference
Installation
Python 3.12 or later is required.
pip install mermaiden
Source generation needs no browser or Mermaid executable. Application.validate_render() additionally requires the
compatible mmdc executable and a browser.
Discover a diagram contract
from mermaiden import Application
with Application.create() as application:
diagrams = application.available_diagrams()
sequence = application.diagram_info("sequenceDiagram")
description = application.diagram_description(sequence.id)
payload_contract = application.command_payload(sequence.id, "add_participant")
payload = payload_contract.validate({"id": "api", "label": "API", "kind": "control"})
assert sequence in diagrams
assert "add_participant" in description.commands
assert payload.values["kind"] == "control"
Application.available_diagrams() returns the runtime catalog. diagram_description() and command_payload() expose
the same strict contracts used by command execution, so an adapter does not need a parallel operation manifest.
Create, persist, and render
from mermaiden import Application
with Application.create() as application:
diagram = application.create_diagram("sequenceDiagram")
change = application.apply_batch(
diagram,
(
{"operation": "add_participant", "arguments": {"id": "client", "label": "Client"}},
{"operation": "add_participant", "arguments": {"id": "api", "label": "API"}},
{
"operation": "add_message",
"arguments": {
"id": "request",
"source_id": "client",
"target_id": "api",
"label": "Request",
},
},
),
)
assert change.can_commit
payload = application.snapshot(diagram).to_dict()
restored = application.restore(payload)
source = application.render(restored)
Snapshots use a closed, versioned envelope with registry-owned identities rather than Python import paths. Drafts may be persisted and restored, but rendering requires every blocking constraint to be resolved. See Persist and restore diagrams for the exact boundary.
To validate the generated source as SVG, first follow the consumer setup in Render and validate Mermaid.
Update, move, and reorder
from mermaiden import Application
with Application.create() as application:
diagram = application.create_diagram("block")
application.execute(diagram, "add_group", {"id": "source", "label": "Source"})
application.execute(diagram, "add_group", {"id": "target", "label": "Target"})
application.execute(
diagram,
"add_block",
{"id": "catalog", "label": "Catalog", "parent_id": "source"},
)
application.execute(
diagram,
"update_element",
{"id": "catalog", "kind": "block_node", "changes": {"label": "Product Catalog"}},
)
application.execute(
diagram,
"move_element",
{"id": "catalog", "kind": "block_node", "parent_id": "target", "position": 0},
)
snapshot = application.snapshot(diagram).to_dict()
restored = application.restore(snapshot)
assert application.render(restored) == application.render(diagram)
The generated mutation contract records update, move, reorder, and retarget semantics and per-diagram coverage. Use Mutate diagrams for task-focused mutation, removal, and atomic-rejection guidance.
Development
Create the development environment and run the fast tier:
uv sync --locked --group dev
make fast-check
The contribution guide covers repository verification and generated contracts. Documentation is built
strictly with make documentation-check; external links are checked with make documentation-linkcheck.
License
Mermaiden is proprietary software. No permission to use, copy, modify, or distribute it is granted without prior express written permission. See LICENSE for the complete terms.
Metadata
Release files for mermaiden 11.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mermaiden-11.0.1.tar.gz | 472.5 kB | With provenance | Details for mermaiden-11.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mermaiden-11.0.1-py3-none-any.whl | Python 3 | none | any | Details for mermaiden-11.0.1-py3-none-any.whl |
Total release size: 737.1 kB
Release files / mermaiden-11.0.1.tar.gz
| Download URL | mermaiden-11.0.1.tar.gz |
|---|---|
| Size | 472.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90ee0efd65b7448f3f3de73f48ad22765a58fb0a7cf1fb2c599669ca48900ebf
|
|
BLAKE2b-256 checksum How to use checksums |
81ff231e86ab115db332e14651aa91c83e398dbd5163b9eef5c09d4095485142
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / mermaiden-11.0.1-py3-none-any.whl
| Download URL | mermaiden-11.0.1-py3-none-any.whl |
|---|---|
| Size | 264.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc86ce579f29bb16dd479413a2b32b0f08ddddf7a6edafd4f7bcf301739923d0
|
|
BLAKE2b-256 checksum How to use checksums |
865de9798b0179cc9541556a657499f6da95e6986b6dcf8740ac03f7d062c121
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for mermaiden 11.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mermaiden-11.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.