deepmerge

v4.3.1

A library for deep (recursive) merging of Javascript objects For more information about how to use this package see README

Latest version published 1 year ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

76 / 100

Explore Similar Packages

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
4.3.1 | 03/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.2.2 | 10/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.3.0 | 06/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.2.1 | 10/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.1.1 | 05/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Key ecosystem project

Weekly Downloads (33,431,945)

Download trend
GitHub Stars
2.73K
Forks
216
Contributors
30

Direct Usage Popularity

TOP 5%

The npm package deepmerge receives a total of 33,431,945 downloads a week. As such, we scored deepmerge popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package deepmerge, we found that it has been starred 2,732 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
30
Funding
No

With more than 10 contributors for the deepmerge repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like deepmerge is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 76/100 package health 76/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
37
Open PR
17
Last Release
1 year ago
Last Commit
1 year ago

Further analysis of the maintenance status of deepmerge based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for deepmerge is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=0.10.0

Age
12 years
Dependencies
0 Direct
Versions
47
Install Size
31.2 kB
Dist-tags
1
# of Files
11
Maintainers
1
TS Typings
No

deepmerge has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.