config

v3.3.7

Configuration control for production node deployments

MIT
Latest version published 4 months ago
    npm install config
  

Package Health Score

84 / 100

Security

No known security issues
Powered by Snyk
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
3.3.7 | 01/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.2.6 | 02/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.2 | 11/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.31.0 | 07/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.30.0 | 02/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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test config
Get started free

Popularity

Influential project

Weekly Downloads (942,484)

Download trend
Dependents
3.49K
GitHub Stars
5.61K
Forks
462
Contributors
90

Direct Usage Popularity

TOP 5%

The npm package config receives a total of 942,484 downloads a week. As such, we scored config popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package config, we found that it has been starred 5,606 times, and that 3,490 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.

Community

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

With more than 10 contributors for the config 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 config is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 84/100 package health 84/100

Maintenance

Healthy

Commit Frequency

Open Issues
50
Open PR
7
Last Release
4 months ago
Last Commit
22 days ago

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

We found that config demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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
>= 10.0.0

Age
11 years
Dependencies
1 Direct
Versions
117
Install Size
92.8 kB
Dist-tags
1
# of Files
9
Maintainers
2
TS Typings
Yes

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