merge-deep

v3.0.3

Recursively merge values in a javascript object.

MIT
Latest version published 1 year ago
    npm install merge-deep
  

Package Health Score

74 / 100

Popularity

Influential project

Weekly Downloads (1,731,427)

Download trend
Dependents
229
GitHub Stars
104
Forks
23
Contributors
2

Direct Usage Popularity

TOP 5%

The npm package merge-deep receives a total of 1,731,427 downloads a week. As such, we scored merge-deep popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package merge-deep, we found that it has been starred 104 times, and that 229 other projects in the ecosystem are dependent on it.

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

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

02/2015
06/2015
12/2015
01/2021

Direct Vulnerabilities

Popular
3.0.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.1.5
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.0.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.1.5
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3
  • 0
    H
  • 0
    M
  • 0
    L
2.0.2
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.0.3
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like merge-deep is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test merge-deep
Keep your project free of vulnerabilities with Snyk

Maintenance

Sustainable

Commit Frequency

No Recent Commits
Open Issues
6
Open PR
5
Last Release
1 year ago
Last Commit
1 year ago

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

An important project maintenance signal to consider for merge-deep 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.

Community

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 74/100 package health 74/100

Package

Node.js Compatibility
>=0.10.0

Age
7 years
Dependencies
3 Direct
Versions
17
Install Size
8.46 kB
Dist-tags
1
# of Files
4
Maintainers
2
TS Typings
No

merge-deep 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.