Is resolve-composer-conflict safe to use?

resolve-composer-conflict has no known vulnerabilities on the latest version (0.3.11). DepScope rates its health at 39/100 (critical risk).

What is the latest version of resolve-composer-conflict?

The latest version of resolve-composer-conflict is 0.3.11, released 2019-12-28.

Does resolve-composer-conflict have known vulnerabilities?

No known vulnerabilities on the latest version of resolve-composer-conflict.

Is resolve-composer-conflict deprecated?

No, resolve-composer-conflict is actively maintained. Latest release: 0.3.11 (2019-12-28).

What are alternatives to resolve-composer-conflict?

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

What license does resolve-composer-conflict use?

resolve-composer-conflict is licensed under MIT.

resolve-composer-conflict

npmv0.3.11

Utility to automatically resolve composer.lock git conflicts

License MITpermissive19 versions1 maintainers2 deps

namoscato/resolve-composer-conflict

/ 100

Health

use with caution

[email protected] low health (39/100) — consider alternatives

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

colors readline-sync

API access

Get this data programmatically — free, no authentication.

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