Is @ljheee/xmind-parser safe to use?

@ljheee/xmind-parser has no known vulnerabilities on the latest version (1.1.3). DepScope rates its health at 51/100 (high risk).

What is the latest version of @ljheee/xmind-parser?

The latest version of @ljheee/xmind-parser is 1.1.3, released 2026-04-01.

Does @ljheee/xmind-parser have known vulnerabilities?

No known vulnerabilities on the latest version of @ljheee/xmind-parser.

Is @ljheee/xmind-parser deprecated?

No, @ljheee/xmind-parser is actively maintained. Latest release: 1.1.3 (2026-04-01).

What are alternatives to @ljheee/xmind-parser?

Popular alternatives to @ljheee/xmind-parser in npm include: ?, minimatch, ansi-styles, brace-expansion, semver.

What license does @ljheee/xmind-parser use?

@ljheee/xmind-parser is licensed under MIT.

@ljheee/xmind-parser

npmv1.1.3

Full-fidelity bidirectional converter between XMind (.xmind) and KityMinder (.km) JSON formats. Supports XMind 8 (XML) and XMind 2020+ (JSON), covering hyperlinks, notes, images, labels, markers, priority, progress, and styles.

License MITpermissive4 versions1 maintainers1 deps1,442 weekly dl

ljheee/xmind-parser

/ 100

Health

use with caution

@ljheee/[email protected] low health (51/100) — consider alternatives

Moderate health score (51/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

6/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@xmldom/xmldom

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@ljheee/xmind-parser