common-config

v0.1.1

Config store for values that are commonly needed by project scaffolders, like Generate or Yeoman.

MIT
Latest version published 2 years ago
    npm install common-config
  

Package Health Score

41 / 100

Popularity

Recognized

Weekly Downloads (21,618)

Download trend
Dependents
6
GitHub Stars
7
Forks
1
Contributors
2

Direct Usage Popularity

Uncommon

The npm package common-config receives a total of 21,618 downloads a week. As such, we scored common-config popularity level to be Recognized.

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

01/2020

Direct Vulnerabilities

Popular
0.1.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

Popular
0.1.1
  • 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 common-config 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 common-config
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of common-config 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 common-config 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
Yes

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 41/100 package health 41/100

Package

Node.js Compatibility
>=0.10.0

Age
6 years
Dependencies
13 Direct
Versions
3
Install Size
13.9 kB
Dist-tags
1
# of Files
6
Maintainers
1
TS Typings
No

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