Is @victr/deepmerge safe to use?

@victr/deepmerge has no known vulnerabilities on the latest version (1.3.2). DepScope rates its health at 36/100 (critical risk).

What is the latest version of @victr/deepmerge?

The latest version of @victr/deepmerge is 1.3.2, released 2023-12-08.

Does @victr/deepmerge have known vulnerabilities?

No known vulnerabilities on the latest version of @victr/deepmerge.

Is @victr/deepmerge deprecated?

No, @victr/deepmerge is actively maintained. Latest release: 1.3.2 (2023-12-08).

What are alternatives to @victr/deepmerge?

Popular alternatives to @victr/deepmerge in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @victr/deepmerge use?

@victr/deepmerge is licensed under MIT.

@victr/deepmerge

npmv1.3.2

Merges the enumerable properties of two or more objects deeply.

License MITpermissive3 versions1 maintainers0 deps278 weekly dl

victrme/deepmerge

/ 100

Health

use with caution

@victr/[email protected] low health (36/100) — consider alternatives

Moderate health score (36/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@victr/deepmerge