← Home

@fastify/deepmerge

npm Repository Homepage

Merges the enumerable properties of two or more objects deeply.

11
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

simonebdelvedormatteo.collinajsumnerszektheommfox1tairhornskibertoadclimba03003galvezsimenbgurgundaymetcoder95jean-micheletivan-tymoshenkofdawgs

Keywords

mergedeeprecursiveobjectimmutable

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): climba03003 is a well-established Fastify org contributor (303 approved packages, 0 rejected). Transition from jsumners is consistent with known Fastify maintainer changes within the official org. ai
provenance no-provenance AI (provenance): Established Fastify org package; lack of Sigstore provenance is a minor hygiene issue, not a security risk for this package. ai

Versions (showing 11 of 11)

Version Deps Published
3.2.1 0 / 5
3.2.0 0 / 5
3.1.0 0 / 5
3.0.0 0 / 5
2.0.2 0 / 5
2.0.1 0 / 5
2.0.0 0 / 4
1.3.0 0 / 4
1.2.0 0 / 4
1.1.0 0 / 3
1.0.0 0 / 3

v3.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

2 findings
HIGH Publisher changed: jsumners → matteo.collina (on 2025-01-31) provenance

This version was published by a different npm account than previous versions on 2025-01-31. 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.

v2.0.1

2 findings
HIGH Publisher changed: jsumners → climba03003 (on 2024-12-23) provenance

This version was published by a different npm account than previous versions on 2024-12-23. 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.

v2.0.0

2 findings
HIGH Publisher changed: matteo.collina → jsumners (on 2024-06-23) provenance

This version was published by a different npm account than previous versions on 2024-06-23. 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.