Weekly GitHub Report for Mermaid: September 22, 2025 - September 29, 2025 (12:04:08)

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.

1. Upon applying text spacing, 'flow chart' text is getting cutoff: This issue describes a problem where text within flow charts is getting cut off when accessibility tools increase letter spacing, violating WCAG guidelines related to text spacing. The user demonstrates that applying custom CSS to increase line height, letter spacing, and word spacing causes diagram labels to be hidden, impacting readability for cognitive and low vision users.

   • The comments acknowledge the issue and suggest that the CSS is applied after the graph renders, recommending the use of themecolours for styling; the original reporter clarifies that the increased spacing is necessary for accessibility purposes and is applied post-rendering to aid users with visual impairments.
   • Number of comments this week: 2

2. In version 11.6, the method mermaid.mermaidAPI.getDiagramFromText has been deprecated. Which method should be used instead? I couldn't find any information about it in the documentation.: This issue concerns the deprecation of the method mermaid.mermaidAPI.getDiagramFromText in version 11.6 of the Mermaid library, with the user seeking guidance on which method should be used as a replacement since the documentation does not provide this information. The user is specifically looking for an alternative API to obtain diagram information, as the deprecated method no longer functions as expected.

   • The maintainers requested more details about the user's use case to provide an appropriate answer, and the user responded by sharing a screenshot illustrating their need to retrieve diagram information using the deprecated method, emphasizing the lack of clarity on the replacement API.
   • Number of comments this week: 2

3. Sequence Diagram "Note over A" KaTeX extra padding: This issue reports a problem with excessive padding when using the "Note over" syntax in Mermaid sequence diagrams with KaTeX-rendered content, whereas using "Note left of" does not exhibit this padding issue. The user provides a minimal reproducible example, screenshots, and details about their environment, highlighting the inconsistency in padding behavior between these two note placements.

   • A contributor responded by creating a pull request and accompanying tests to address the padding problem, requesting feedback on any further requirements or improvements.
   • Number of comments this week: 1

4. dagre-d3-es-7.0.11.tgz Vulnerabilities: This issue reports a prototype pollution vulnerability in the dagre-d3-es Node.js package versions earlier than 7.0.11, caused by improper sanitization of user input in the addConflict function of the bk module. This flaw allows attackers to inject malicious property keys like "proto", potentially leading to denial of service, application crashes, or arbitrary code execution, and the suggested fix is to update to version 7.0.12.

   • The comment clarifies that version 7.0.12 of dagre-d3-es does not exist and provides a link to a related issue in the dagre-es repository, indicating that the proposed solution in the original report is not currently available.
   • Number of comments this week: 1

5. Mindmap rendering broken when the number of level 2 nodes exceeds 11: This issue describes a problem with rendering mindmap diagrams in the Mermaid library when the number of level 2 nodes exceeds 11. Specifically, nodes from the 12th onward are incorrectly colored black and remain disconnected from the rest of the graph, affecting both the standalone library and the Live Editor.

   • The single comment expresses agreement with the issue, indicating that others have experienced or acknowledge the problem.
   • 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.

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 explaining their significance, which can lead to 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, enabling logarithmic scaling of charts. This enhancement aims to allow users to version control graph data with true values while displaying the data on a logarithmic scale, with potential for future extension to other scale types.
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 to a reliance on Markdown titles as a workaround.
4. SVG rendering formatting issues with markdown input: This issue addresses problems with SVG rendering when nodes in a diagram use markdown formatting, resulting in inconsistent visual output such as added height or text being cut off in the SVG files generated by the Mermaid live editor. Specifically, the issue occurs both when opening the SVG in a new tab and when downloading the SVG, causing formatting discrepancies that affect the appearance and readability 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, the build process fails on application startup with a TypeError related to setting properties on an undefined object, specifically involving Mermaid's API initialization and rendering.

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

Summarized Issues:

• Rendering issues in diagrams: Multiple problems affect the rendering of Mermaid diagrams, including incorrect newline character display in class diagram notes, duplicate interface objects in class diagrams with Lollipop Interface markup, and mindmap diagrams failing to render correctly when exceeding 11 level 2 nodes. Additionally, graph rendering crashes when node labels contain parentheses, and excessive padding occurs around "Note over" syntax in sequence diagrams with KaTeX expressions, all impacting the visual correctness of diagrams.
• issues/6974, issues/6980, issues/6993, issues/7000, issues/7002

• Text formatting and accessibility problems: Text wrapping breaks in the Mermaid Editor when browser zoom is changed from 100%, and increasing text spacing for accessibility causes flowchart text to be hidden or cut off, violating WCAG guidelines. There is also an issue where double-quoted text in flowcharts is incorrectly processed as Markdown formatting, causing unintended HTML tag transformations contrary to documentation.
• issues/6982, issues/6986, issues/7003

• Feature requests for diagram enhancements: Users have proposed adding automatic sequence numbering in sequence diagrams to count messages from both sender and receiver sides, including self-messages, and a new syntax to link foreign key columns directly to primary keys in entity-relationship diagrams to improve clarity in complex models.
• issues/6988, issues/7005

• API and usage guidance issues: There is a request for guidance on the replacement method for the deprecated mermaid.mermaidAPI.getDiagramFromText in version 11.6, as no documentation currently explains the new method to obtain diagram information.
• issues/6990

• Security vulnerability: A prototype pollution vulnerability exists in the dagre-d3-es Node.js package versions prior to 7.0.11, where improper sanitization in the bk module's addConflict function allows injection of malicious property keys like "proto", potentially leading to denial of service, crashes, or arbitrary code execution.
• issues/6998

• Critical bugs in recent versions: Mermaid version 11.12.0 introduces a regression causing a TypeError due to an undefined internal clusterDb.keys function during flowchart rendering, blocking rendering especially in mobile Cordova apps using dynamic imports. Additionally, a parsing error occurs in the same version when using backslashes in math formulas inside new flowchart shape syntax, causing bugs with formulas enclosed in double quotes.
• issues/7006, issues/7007

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

Summarized Issues:

• Spam and Irrelevant Posts: Some issues, such as "Aggronite," are spam or irrelevant with no substantive proposal, use cases, syntax, or implementation details. These posts also include off-topic comments expressing frustration about spam behavior, which detracts from productive discussion.
• issues/6969

• Minimal or Unclear Issue Reports: There are reports like "master" that provide minimal description and lack additional context or suggested solutions, making it difficult to address or prioritize them effectively. These issues do not contribute meaningful information to the project’s development.
• issues/6987

• Multi-line Flowchart Support: A key challenge discussed is the inability to create multi-line flowcharts with nodes arranged across different directional flows within the same diagram. This feature is currently unsupported but is planned for future implementation to enhance diagram flexibility.
• issues/6991

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.

1. Aggronite
   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, legal threats)
   • This GitHub conversation involves multiple users where the initial comment uses informal and potentially offensive language, prompting a response that references legal action and expresses frustration. Another participant criticizes the perceived spamming behavior, contributing to a tense and confrontational tone throughout the exchange.

---

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

Key Open Pull Requests

1. Enhancement/2880 er click support: This pull request adds click interaction support for erDiagram entities in Mermaid, enabling linking to URLs, in-page anchors, and callback functions, thereby enhancing interactivity similar to flowChart diagrams and resolving issues #2880 and #3966.

• URL: pull/6985

• Merged: No

• Associated Commits: 3e813, 0385c, b2c5c, a5df4, 8d01f, 859ce, c13a7, db81d, 09209, 971a9, 129b3

2. Bug/6993 note over katex padding: This pull request fixes the padding issue for KaTeX notes over a single actor in sequence diagrams by removing unnecessary recalculations of text dimensions when a message is directed to itself, includes added rendering tests to verify consistent KaTeX note positioning, and ensures all existing tests pass.

• URL: pull/6994

• Merged: No

• Associated Commits: 367b9, f745e, acda9, ba99f, 2b9d5, d3c2e

3. feat(git): add gitBranchLabelFontSize theme variable: This pull request introduces a new theme variable gitBranchLabelFontSize that allows users to customize the font size of branch labels in git diagrams, aligning with existing font size variables for commits and tags, and includes necessary tests, documentation updates, and a changeset for proper versioning.

• URL: pull/6971

• Merged: No

• Associated Commits: d8875, 63bc2, e1b3a, e9764, fcb1b

Other Open Pull Requests

• Bug fixes in diagram rendering and parsing: Multiple pull requests address bugs in various diagram types including ER diagrams, Sankey diagrams, block diagrams, and flowchart parsing. These fixes improve grammar parsing for special characters and directions, correct node width calculations, and stabilize visual elements like link thickness and text wrapping.
• pull/6984, pull/6970, pull/6989, pull/6999, pull/6983

• Text formatting improvements: Pull requests improve text formatting in diagrams by replacing newline characters with HTML line breaks and enabling proper text wrapping in text creation features. These changes enhance readability and presentation in class diagrams and other text elements.
• pull/6975, pull/6983

• Configuration deprecation and refactoring: One pull request deprecates the flowchart.htmlLabels configuration option by centralizing HTML label settings to a root-level config, adding helper functions for precedence, and updating tests and schema. This streamlines configuration management and issues deprecation warnings for the old option.
• pull/6995

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

Key Closed Pull Requests

1. Added Functionality for the development page: This pull request adds a new interactive Mermaid editor to the development page featuring a split-pane layout with manual and auto-render controls, quick example templates for common diagram types, enhanced error handling, session persistence via localStorage, and a modern, responsive UI integrated with the existing development server workflow.

• URL: pull/7001

• Merged: No

• Associated Commits: b02e7, 3af4b, c6c52, b753d, 65435

2. ci(codeql): enable CodeQL for GitHub Actions: This pull request enables CodeQL scanning for GitHub Actions workflows in the project’s continuous integration setup to enhance security by detecting vulnerabilities in action workflows, leveraging the newly added support announced in December 2024.

• URL: pull/6997

• Merged: Yes

• Associated Commits: 6e675

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.

Contributor	Commits	Pull Requests	Issues	Comments
shubhamparikh2704	39	0	1	6
darshanr0107	41	5	0	0
omkarht	14	2	0	1
knsv	13	0	0	0
sidharthv96	9	0	0	0
y76	6	1	1	1
No author found	9	0	0	0
Copilot	1	0	0	5
Raj4478	5	1	0	0
aloisklink	3	1	0	0