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/parser@0.4.0

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.

As of our latest update, there are no active issues with ongoing comments this week.

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.

1. Tooltips for emoji in Diagram Syntax doc tree: This issue proposes adding tooltips to the emoji displayed next to the names of various diagram types in the "Diagram Syntax" section of the documentation tree. The goal is to help users understand the meaning of these icons, as currently there is no reference or explanation available, causing confusion even for experienced users.
2. log scale for xychart-beta: This issue proposes adding a scale string field to the xychart-beta component that defaults to linear but can also accept log as an option, with the potential to support additional scales in the future. This enhancement would enable users to maintain version control over graph data using true (non-logged) values while displaying the data on a logarithmic scale for more effective visualization.
3. Unable to Style Sequence Diagram Title: This issue describes a problem where users are unable to change the font size of the title in sequence diagrams created with Mermaid, resulting in titles that appear very small and difficult to read. The reporter notes that while other diagram types in Mermaid support title styling attributes, such as font size, this functionality is not yet available for sequence diagrams, leading them to use a Markdown title as a temporary workaround.
4. SVG rendering formatting issues with markdown input: This issue addresses problems with SVG rendering when nodes contain markdown-formatted text in diagrams, specifically causing additional height to be added or text to be cut off in the SVG output. These formatting inconsistencies occur both when opening the SVG in a new tab and when downloading the SVG from the editor, affecting the visual accuracy of the rendered diagrams.
5. Vite build error with mermaid version 10.9.0: This issue describes a problem encountered when building a Vue 3 and Vite application that uses Mermaid version 10.9.0 to render graphs. While the development server runs without errors and displays the graphs correctly, the build process results in a runtime error related to setting properties on an undefined object, causing the application to fail on startup.

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: 5

Summarized Issues:

• UI and Diagram Layout Improvements: Several issues highlight the need for better diagram representation and layout handling in Mermaid. These include proposals for a dedicated UI layout diagram type to improve communication among teams and problems with diagram controls overlapping content, which affect usability and visibility.
• [issues/7111, issues/7117]

• Diagram Rendering and Alignment Bugs: There are reported bugs related to diagram rendering, such as misalignment of connecting lines in flowcharts when using invisible nodes, which varies across Mermaid versions. These issues impact the visual accuracy and clarity of diagrams, causing inconsistencies in node connections.
• [issues/7118]

• Class Diagram Annotation Errors: The recommended use of inline annotations with class definitions in Mermaid class diagrams causes errors in the playground and markdown environments. This discrepancy between documentation and actual functionality needs fixing to ensure proper diagram rendering.
• [issues/7114]

• Sankey Diagram Feature Requests: There is a request to add support for backward flow or loops in Sankey diagrams to better represent thermodynamic cycles that reuse power. Currently, the lack of loop capabilities limits the ability to depict these efficient cycles accurately.
• [issues/7119]

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: 1

Summarized Issues:

• Radar Chart Rendering Issues: The radar chart feature in the Mermaid project is experiencing problems with rendering and parsing correctly. These issues prevent users from visualizing radar charts as intended, impacting the usability of this chart type.
• issues/7112

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: 4

Key Open Pull Requests

1. feat: Support icons in config: This pull request introduces native support for Iconify-compatible icon packs in Mermaid via a declarative configuration in MermaidConfig, enabling consistent, secure, and lazy-loaded icon rendering across browsers, CLI, Live Editor, and hosted renderers without requiring custom JavaScript, while enforcing version pinning, host allowlisting, size limits, and backward compatibility.

• URL: pull/7113

• Merged: No

• Associated Commits: a23c2, 17203, df218, c6071, c24a1, 25d96, 928ae, 525e6, f8a0a

2. 7022: Fix parser error when service IDs start with edge direction letters (L, R, T, B): This pull request fixes a parser error in the Mermaid project that occurs when service IDs start with edge direction letters (L, R, T, B), ensuring that architecture diagram parsing no longer fails in these cases.

• URL: pull/7106

• Merged: No

• Associated Commits: f7d7f

3. docs: Add speccharts to integrations-community.md: This pull request adds a new entry for the open-source CLI tool speccharts, which generates Mermaid flowcharts from JavaScript/TypeScript test suites, to the integrations-community.md documentation file.

• URL: pull/7109

• Merged: No

• Associated Commits: c7f8a

Other Open Pull Requests

• HTML entity handling in diagram parsers: This pull request fixes inconsistent handling of the # character in exclusion patterns within lexer rules across multiple diagram parsers. It ensures that titles containing # are parsed correctly in all diagram types and includes a comprehensive test suite to validate the fix.
• pull/7110

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. fix: update dagre-d3-es to version 7.0.13: This pull request updates the dagre-d3-es dependency to version 7.0.13 to address the security vulnerability CVE-2025-57347 caused by improper sanitization of user input in earlier versions, ensuring that automated tools no longer flag this dependency despite Mermaid not directly using the vulnerable function.

• URL: pull/7107

• Merged: Yes

• Associated Commits: cbf89, 06163

2. temp: validation test: This pull request is a temporary validation test involving an incorrect lockfile commit that was subsequently reverted and was not merged into the main project.

• URL: pull/7115

• Merged: No

• Associated Commits: acf58, 3b754

3. fix: Lockfile validation: This pull request fixes the lockfile validation process by preventing duplicate comments in the validation workflow and enabling the workflow to run on forked repositories.

• URL: pull/7116

• Merged: Yes

• Associated Commits: e7719, 58137

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.