merge-deep
Recursively merge values in a javascript object.
10
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
jonschlinkertdoowb
Keywords
cloneclone-deepcopydeepdeep-clonedeep-mergeextendkeykeysmergemerge-deepobjectobjectsproppropertiespropertypropsvaluevalues
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): doowb (Brian Woodward) is a long-time collaborator of jonschlinkert in the same open-source ecosystem; this is a legitimate maintainer transition, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a trusted collaborator publishing a minor update with no code changes is consistent with legitimate maintenance, not account compromise. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 3 / 2 | |
| 1.0.3 | 2 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.1.5 | 3 / 2 | |
| 0.1.4 | 3 / 2 | |
| 0.1.3 | 3 / 4 | |
| 0.1.2 | 2 / 4 | |
| 0.1.0 | 3 / 4 |
v3.0.3
2 findings
HIGH
Publisher changed: jonschlinkert → doowb (on 2021-01-11)
provenance
This version was published by a different npm account than previous versions on 2021-01-11. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.