Is @trenskow/merge safe to use?

@trenskow/merge has no known vulnerabilities on the latest version (0.1.53). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of @trenskow/merge?

The latest version of @trenskow/merge is 0.1.53, released 2026-03-28.

Does @trenskow/merge have known vulnerabilities?

No known vulnerabilities on the latest version of @trenskow/merge.

Is @trenskow/merge deprecated?

No, @trenskow/merge is actively maintained. Latest release: 0.1.53 (2026-03-28).

What are alternatives to @trenskow/merge?

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

What license does @trenskow/merge use?

@trenskow/merge is licensed under BSD-2-Clause.

@trenskow/merge

npmv0.1.53

A small library for doing recursive `Object.assign`.

License BSD-2-Clausepermissive53 versions1 maintainers0 deps

trenskow/merge

/ 100

Health

safe to use

@trenskow/[email protected] is safe to use (health: 62/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@trenskow/merge