Is parse-conflict-json safe to use?

parse-conflict-json has no known vulnerabilities on the latest version (6.0.0). DepScope rates its health at 83/100 (low risk).

What is the latest version of parse-conflict-json?

The latest version of parse-conflict-json is 6.0.0, released 2026-05-15.

Does parse-conflict-json have known vulnerabilities?

No known vulnerabilities on the latest version of parse-conflict-json.

Is parse-conflict-json deprecated?

No, parse-conflict-json is actively maintained. Latest release: 6.0.0 (2026-05-15).

What are alternatives to parse-conflict-json?

Popular alternatives to parse-conflict-json in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does parse-conflict-json use?

parse-conflict-json is licensed under ISC.

parse-conflict-json

npmv6.0.0

Parse a JSON string that has git merge conflicts, resolving if possible

License ISCpermissive13 versions4 maintainers3 deps4,931,414 weekly dl

npm/parse-conflict-json

83

/ 100

Health

safe to use

[email protected] is safe to use (health: 83/100)

Health breakdown0 – 100

25/25

maintenance

17/20

popularity

25/25

security

12/15

maturity

4/15

community

0/15

popularity_floor

Vulnerabilities

0

none known

Bundle & TypeScript

🌟

TypeScript

7/10typed

Types from @types/parse-conflict-json (DefinitelyTyped)

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (3)

json-parse-even-better-errors just-diff just-diff-apply

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/parse-conflict-json