Deeply merge 2 or more objects respecting type information.
86%
Total Score
75
100
94
70
100
One of 17 workflows uses pull_request_target, but no untrusted checkout or script-injection patterns were detected. The isolated use is worth awareness but is not a severe health concern on these results.
The package uses a prepare install-time lifecycle script, which adds execution during installation. This is a modest supply-chain and reproducibility concern, though the package also provides a built dist tree and has build tooling in the repository.
The repository is owned by an individual rather than an organization, so there is no organizational succession signal to offset the concentrated maintainer base. The active owner still provides clear accountability.
One human contributor made 44 of 48 recent commits, while the other four were made by semantic-release-bot. This concentrated human ownership creates a meaningful continuity risk despite the recent activity.
The project uses TypeScript, Rollup, Vitest, and related build tooling, supporting a reproducible development process. No security scanning tools were detected, leaving a modest security-process gap.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-40345 deepmerge-ts is vulnerable to Uncontrolled Recursion in versions 0.0.0 - 8.0.0. | 0.0.0 - 8.0.0 | High |
CVE-2022-24802 deepmerge-ts is vulnerable to Improperly Controlled Modification of Dynamically-Determined Object Attributes in versions 0.0.0 - 4.0.2. | 0.0.0 - 4.0.2 | High |
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.