Is @pnpm/merge-lockfiles safe to use?

@pnpm/merge-lockfiles has no known vulnerabilities on the latest version (0.0.0-20201030124). DepScope rates its health at 68/100 (moderate risk).

What is the latest version of @pnpm/merge-lockfiles?

The latest version of @pnpm/merge-lockfiles is 0.0.0-20201030124, released 2020-11-03.

Does @pnpm/merge-lockfiles have known vulnerabilities?

No known vulnerabilities on the latest version of @pnpm/merge-lockfiles.

Is @pnpm/merge-lockfiles deprecated?

No, @pnpm/merge-lockfiles is actively maintained. Latest release: 0.0.0-20201030124 (2020-11-03).

What are alternatives to @pnpm/merge-lockfiles?

Popular alternatives to @pnpm/merge-lockfiles in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @pnpm/merge-lockfiles use?

@pnpm/merge-lockfiles is licensed under MIT.

@pnpm/merge-lockfiles

npmv0.0.0-20201030124

Merges lockfiles. Can automatically fix merge conflicts

License MITpermissive1 versions2 maintainers3 deps2 weekly dl

pnpm/pnpm

/ 100

Health

use with caution

@pnpm/[email protected] low health (68/100) — consider alternatives

Moderate health score (68/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

11/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

@pnpm/lockfile-types ramda semver

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/merge-lockfiles