Is @types/deepmerge safe to use?

@types/deepmerge has no known vulnerabilities on the latest version (2.2.3). DepScope rates its health at 14/100 (critical risk).

What is the latest version of @types/deepmerge?

The latest version of @types/deepmerge is 2.2.3, released 2024-10-23.

Does @types/deepmerge have known vulnerabilities?

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

Is @types/deepmerge deprecated?

Yes, @types/deepmerge is deprecated: This is a stub types definition. deepmerge provides its own type definitions, so you do not need this installed. Consider using ? instead.

What are alternatives to @types/deepmerge?

Popular alternatives to @types/deepmerge in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @types/deepmerge use?

@types/deepmerge is licensed under MIT.

@types/deepmerge

npmv2.2.3deprecated

Stub TypeScript definitions entry for deepmerge, which provides its own types definitions

License MITpermissive9 versions1 maintainers1 deps

/ 100

Health

find alternative

@types/deepmerge is deprecated — find an alternative

Moderate health score (14/100) — verify manually
Package is deprecated

Health breakdown0 – 100

5/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 (1)

deepmerge

API access

Get this data programmatically — free, no authentication.

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