merge-dictionaries

v1.0.0

Recursively merge two dictionaries together

MIT
Latest version published 5 years ago
    npm install merge-dictionaries
  
We couldn't find any similar packages Browse all packages

Package Health Score

44 / 100

Popularity

Recognized

Weekly Downloads (26,014)

Download trend
Dependents
5
GitHub Stars
0
Forks
1
Contributors
1

Direct Usage Popularity

TOP 30%

The npm package merge-dictionaries receives a total of 26,014 downloads a week. As such, we scored merge-dictionaries popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package merge-dictionaries, we found that it has been starred ? times, and that 5 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

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

02/2017
03/2017

Direct Vulnerabilities

Popular
0.0.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.0.3
1.0.0

License Risk

Popular
0.0.3
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0
  • 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-dictionaries 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-dictionaries
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
1
Last Release
5 years ago
Last Commit
5 years ago

Further analysis of the maintenance status of merge-dictionaries 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 merge-dictionaries 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
1
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 44/100 package health 44/100

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
1 Direct
Versions
4
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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