Is @pnpm/merge-lockfile-changes safe to use?

@pnpm/merge-lockfile-changes has no known vulnerabilities on the latest version (6.0.5). DepScope rates its health at 45/100 (high risk).

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

The latest version of @pnpm/merge-lockfile-changes is 6.0.5, released 2024-07-21.

Does @pnpm/merge-lockfile-changes have known vulnerabilities?

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

Is @pnpm/merge-lockfile-changes deprecated?

No, @pnpm/merge-lockfile-changes is actively maintained. Latest release: 6.0.5 (2024-07-21).

What are alternatives to @pnpm/merge-lockfile-changes?

Popular alternatives to @pnpm/merge-lockfile-changes in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @pnpm/merge-lockfile-changes use?

@pnpm/merge-lockfile-changes is licensed under MIT.

@pnpm/merge-lockfile-changes

npmv6.0.5

Merges lockfiles. Can automatically fix merge conflicts

License MITpermissive43 versions2 maintainers5 deps

pnpm/pnpm/blob/main/lockfile/merge-lockfile-changes

/ 100

Health

safe to use

@pnpm/[email protected] is safe to use (health: 45/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (5)

comver-to-semver ramda semver @pnpm/lockfile-types @pnpm/types

API access

Get this data programmatically — free, no authentication.

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