Make sure the open source you're using is safe to use
user-settings
v0.2.0Simple user settings management
npm install user-settings
Explore Similar Packages
Package Health Score
42 / 100
- Popularity Limited
- Maintenance Inactive
- Security No known security issues
- Community Limited
Make sure the open source you're using is safe to usePopularity
Limited
Weekly Downloads (611)- Dependents
- 44
- GitHub Stars
- 11
- Forks
- 3
- Contributors
- 2
The npm package user-settings receives a total of 611 downloads a week. As such, we scored user-settings popularity level to be Limited.
Based on project statistics from the GitHub repository for the npm package user-settings, we found that it has been starred 11 times, and that 44 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
Security and license risk for significant versions
All VersionsDirect Vulnerabilities
0.1.5
0.2.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
Indirect Vulnerabilities
0.1.5
0.2.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
License Risks
0.1.5
0.2.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
All security vulnerabilities belong to
production dependencies of direct and indirect
packages.
We found a way for you to contribute to the project! Looks like user-settings 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.
We found a way for you to contribute to the project! Looks like user-settings is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test user-settings
Maintenance
Inactive
Commit Frequency- Open Issues
- 1
- Merged PR
- 1
- Open PR
- 1
- Last Commit
- 3 years ago
Further analysis of the maintenance status of user-settings 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 user-settings 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 user-settings is missing a Code of Conduct.
Embed Package Health Score Badge
Package
- Node.js Compatibility
- not defined
- Age
- 7 years
- Dependencies
- 0 Direct
- Versions
- 6
- Install Size
- 0 B
- Dist-tags
- 1
- # of Files
- 0
- Maintainers
- 1
- TS Typings
- No
user-settings 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.