Is detect-conflict safe to use?

detect-conflict has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of detect-conflict?

The latest version of detect-conflict is 1.0.1, released 2016-07-04.

Does detect-conflict have known vulnerabilities?

No known vulnerabilities on the latest version of detect-conflict.

Is detect-conflict deprecated?

No, detect-conflict is actively maintained. Latest release: 1.0.1 (2016-07-04).

What are alternatives to detect-conflict?

Popular alternatives to detect-conflict in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does detect-conflict use?

detect-conflict is licensed under MIT.

detect-conflict

npmv1.0.1

Small utility library that check if a new file content can be merged safely in the on-disk existing file.

License MITpermissive2 versions1 maintainers0 deps

SBoudrias/detect-conflict

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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