defaults

v1.0.3

merge single level defaults over a config object

MIT
Latest version published 6 years ago
    npm install defaults
  

Package Health Score

65 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Influential project
Download trend

Weekly Downloads (7,405,409)

Dependents
571
GitHub Stars
37
Forks
3
Contributors
2

The npm package defaults receives a total of 7,405,409 downloads a week. As such, we scored defaults popularity level to be Influential project.

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

10/2015

Direct Vulnerabilities

Popular
1.0.3
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
1.0.3
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.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 defaults 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 defaults
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of defaults 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 defaults 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 65/100 package health 65/100

Package

Node.js Compatibility
not defined

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

defaults 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.