@mermaid-js/parser

npm

Is @mermaid-js/parser safe to use?

The latest brin safety scan flagged @mermaid-js/parser v0.6.3 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 85/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

@mermaid-js/parser Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • Can spawn child processes

brin Recommendations

  • This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add @mermaid-js/parser to automatically apply these checks before installation.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

@mermaid-js/parser Capabilities & Permissions

What @mermaid-js/parser can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Process Spawning

This package can spawn child processes.

AGENTS.md for @mermaid-js/parser

Good instructions lead to good results. brin adds @mermaid-js/parser documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

@mermaid-js/parser Documentation & Source Code

For the full @mermaid-js/parser README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @mermaid-js/parser safety

Weekly Downloads

2.6M

Version

0.6.3

License

MIT

Other Versions

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes