Weekly GitHub Report for Mermaid

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is @mermaid-js/[email protected]

1.2 Version Information:

On March 25, 2025, a minor update was released that introduced the addition of a Radar Chart, enhancing the charting capabilities of the platform. This update reflects ongoing efforts to expand visualization options.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. [TYPE: BUG / ERROR] [STATUS: TRIAGE] direction inside subgraphs is ignored: This issue reports that specifying a direction inside a subgraph block in Mermaid flowchart diagrams is ignored when nodes inside the subgraph link to nodes outside, causing the subgraph to inherit the global layout direction instead of respecting its own. This behavior is misleading because the direction statement does not produce an error, giving the false impression that subgraph direction is supported, which complicates creating complex flows with mixed layout directions.

   • The comments confirm the issue is a known limitation where subgraphs linked externally inherit the parent graph’s direction, causing confusion. Users express frustration with this behavior and request options to override it or alternative grouping methods. Some progress is noted with partial fixes for orientation inside subgraphs, but related layout problems and feature requests remain open.
   • Number of comments this week: 2

2. [TYPE: ENHANCEMENT] [STATUS: TRIAGE] [CONTRIBUTOR NEEDED] [STATUS: APPROVED] [DISCUSSION] [INTERNALS: LAYOUT] Add support for big diagrams with a configurable ratio: This issue requests adding support for big diagrams with a mixed orientation that combines top-down and left-right layouts to better fit specific aspect ratios like A4 portrait or landscape, aiming to prevent overly tall or wide diagrams. The proposal includes enabling configurable ratios between height and width and possibly introducing local orientation constraints or invisible layout groups to improve automatic layout without requiring fully manual adjustments.

   • The comments discuss the feasibility of mixing orientations within a single diagram, noting current limitations in layout algorithms like Elk and Dagre. Contributors explore workarounds using subgraphs with different directions, express the need for local orientation constraints, and consider adding support for aspect ratio settings, while acknowledging that full mixed-orientation support would require significant changes or new layout algorithms.
   • Number of comments this week: 2

3. [TYPE: ENHANCEMENT] [STATUS: TRIAGE] Syntax Proposal: Extensible Plugin-Based Syntax for Custom Diagram Types: This issue proposes adding a plugin-based syntax extension mechanism to Mermaid.js that allows developers to define and register custom diagram types and extend existing syntax without modifying the core library. The goal is to enable scalable, maintainable, and community-driven innovation by supporting domain-specific diagrams through modular plugins that handle parsing, transformation, and rendering.

   • The comments discuss adding a typed intermediate model between the parser and renderer to improve plugin design, making AI-assisted diagram generation safer and easier to audit. Another comment supports the idea and suggests adding custom decorators and hooks for executable flow diagrams, while a third comment requests more detail on current limitations and improvements for external diagram support.
   • Number of comments this week: 2

4. [TYPE: ENHANCEMENT] [CONTRIBUTOR NEEDED] [STATUS: APPROVED] [GRAPH: CLASS] [GOOD FIRST ISSUE!] Please add association class support to classDiagram syntax: This issue requests the addition of support for UML association classes in Mermaid's classDiagram syntax, as currently there is no way to represent relationships involving an association class between two other classes. The user suggests extending the syntax to allow a class to be placed in the middle of a relationship line, rendering a standard UML association class with a solid line between the two classes and a dashed line connecting the association class to that relationship.

   • The comments discuss possible syntax approaches, including mimicking PlantUML notation or creating a new Mermaid-specific syntax, with some users sharing workarounds and expressing the need for this feature. There is acknowledgment of the issue's importance, updates on active development after a delay, and encouragement for community contributions to implement the feature.
   • Number of comments this week: 1

5. [TYPE: BUG / ERROR] [STATUS: APPROVED] [GRAPH: SEQUENCE] [GOOD FIRST ISSUE!] Sequence Diagram "Note over A" KaTeX extra padding: This issue reports that when using the "Note over" syntax in sequence diagrams with KaTeX expressions, an excessive amount of padding is added compared to using "Note left of," which displays the padding correctly. The user provides code samples and screenshots to demonstrate the problem occurring in Mermaid versions 11 and 12 across multiple browsers, seeking a fix for the inconsistent padding behavior.

   • The comments include a contributor announcing a pull request with tests addressing the issue, followed by another user expressing interest in working on the fix, explaining the root cause related to unnecessary recalculation of text dimensions, and requesting assignment to submit a new pull request.
   • Number of comments this week: 1

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 2

Summarized Issues:

• Diagram Support and Visualization Issues: This topic covers the lack of native support for certain diagram types and rendering inconsistencies in Mermaid. One issue highlights the absence of Venn diagram support, which limits the ability to clearly represent set relationships and classifications, while another issue points out that stadium-shaped nodes do not properly display dashed stroke styles, unlike rectangular nodes which render them correctly.
• issues/7967, issues/7969

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 2

Summarized Issues:

• Flowchart Creation and Process Detailing: This topic covers the creation of a detailed flowchart diagram that outlines the step-by-step process for citizens and police officers in handling card issuance requests. It includes both direct and online submission methods, verification steps, fee payment, and card receipt options, ensuring clarity in the procedural flow.
• issues/7960

• Flowchart Direction Property Bug: This topic addresses a problem where setting the "direction" property inside a subgraph in a Mermaid flowchart breaks the links between nodes inside the subgraph and nodes outside of it. This issue was introduced in version 11.16.0 and was not present in version 11.15.0, affecting flowchart integrity.
• issues/7965

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 5

Key Open Pull Requests

1. feat(shapes): add folder, bucket, console and browser shapes: This pull request adds four new general-purpose flowchart node shapes—folder (alias directory), bucket, console (terminal window), and browser—to the Mermaid diagramming tool, featuring both classic and hand-drawn rendering styles, shape-specific edge intersection behavior, theme-variable–driven decoration colors, comprehensive tests, updated documentation, and improvements to rendering stability and shape registration.

• URL: pull/7970

• Associated Commits: dcfda, b7fe4, 9d994, 9cbcc, cab05, 8f493, d67ed, af249, c6746

2. fix: upgrade glob to 11.1.0, 10.5.0 (CVE-2025-64756): This pull request upgrades the glob package from versions 10.4.5 and 10.5.0 to fixed versions 11.1.0 and 10.5.0 respectively in order to address the high-severity command injection vulnerability identified as CVE-2025-64756, ensuring the fix is applied via pnpm.overrides and verified through build and security scanner re-scans.

• URL: pull/7973

• Associated Commits: 35011, 4ae1c

3. Fix flowchart arrowheads not following edge color from linkStyle and themes: This pull request fixes a long-standing issue in Mermaid flowcharts where arrowheads did not inherit the edge stroke color set via linkStyle or theme variables by updating arrow marker SVG attributes to use context-stroke for color inheritance in supported browsers and improving the fallback mechanism for unsupported browsers to correctly clone and apply per-color markers, ensuring arrowheads match their edge colors accurately across different rendering engines.

• URL: pull/7974

• Associated Commits: d6f91, 34186

Other Open Pull Requests

• Bug fix in Gantt diagram parser: This pull request addresses a bug where invalid or malformed task end duration tokens caused tasks to collapse to zero width silently. It updates the getEndDate function to throw a syntax error on invalid inputs, aligning error handling with that of invalid start dates, and includes tests to ensure proper error propagation.
• pull/7971

• Flowchart alias test suite update: This pull request adds the missing aliasSet40 containing the collate and hourglass alias pair to the flowchart alias test suite. This restores visual regression coverage for that alias pair, improving test completeness.
• pull/7972

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 3

Key Closed Pull Requests

1. feat: add @mermaid-js/mermaid-interactive diagrams package: This pull request proposes adding a new workspace package, @mermaid-js/mermaid-interactive, which extends Mermaid diagrams by enabling click-to-collapse/expand interactivity and tooltip overlays through a two-layer design involving a build-time preprocessor and a runtime binder, all implemented without modifying the core Mermaid library or its renderer, thereby preserving compatibility and graceful degradation across different environments.

• URL: pull/7700

• Associated Commits: b3dd0, 98c4d, e01bb, f69db, 1b288, d3a1a, c7175, a8dbf, dec7c, 5d5ab, 47667, 573a2, 9bae6, e4c83, 200db, 8fe87, f2e83, d6e14, 054a1, f435a, 6470c, 5d9c6, 4a7f4, be2eb, 5c631, ee0eb, 88c39, a65b6, 0201f, 47ce8, 9d5e0, e3523, 18df5, f1e7d, fee8a, bbab1, dced2, c5284, f8755, 8fbe7, 2e1bb, 7ce3f, d0a72, 4841e

• Associated Commits: b3dd0, 98c4d, e01bb, f69db, 1b288, d3a1a, c7175, a8dbf, dec7c, 5d5ab, 47667, 573a2, 9bae6, e4c83, 200db, 8fe87, f2e83, d6e14, 054a1, f435a, 6470c, 5d9c6, 4a7f4, be2eb, 5c631, ee0eb, 88c39, a65b6, 0201f, 47ce8, 9d5e0, e3523, 18df5, f1e7d, fee8a, bbab1, dced2, c5284, f8755, 8fbe7, 2e1bb, 7ce3f, d0a72, 4841e

2. fix(flowchart): apply ELK mergeEdges in subgraphs: This pull request aims to fix issue #7659 by propagating the ELK mergeEdges option to subgraph layout configurations in flowcharts, ensuring that edge merging works consistently within nested subgraphs as it does at the root level, while preserving existing root graph options and explicit-direction behaviors, and includes a regression test to validate the fix.

• URL: pull/7703

• Associated Commits: e40c6, a4e80

• Associated Commits: e40c6, a4e80

3. Update reference to initialize() call in documentation: This pull request updates the documentation by correcting the reference link for the initialize() call to point to the new _4-calling-the-mermaid-javascript-api anchor in the syntax-reference.md file within both the packages/mermaid/src/docs/intro/ directory and the top-level docs/intro/ copy.

• URL: pull/7963

• Associated Commits: fcb12, 06a19

• Associated Commits: fcb12, 06a19

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.

Access Last Week's Newsletter:

• Link