@purest/providers

v1.0.4

REST API providers configuration for the Purest module

Apache-2.0
Latest version published 1 year ago
    npm install @purest/providers
  

Package Health Score

54 / 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
1.0.4 | 01/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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 @purest/providers
Get started free

Popularity

Recognized

Weekly Downloads (59,214)

Download trend
Dependents
17
GitHub Stars
9
Forks
15
Contributors
4

Direct Usage Popularity

TOP 30%

The npm package @purest/providers receives a total of 59,214 downloads a week. As such, we scored @purest/providers popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package @purest/providers, we found that it has been starred 9 times, and that 17 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

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

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like @purest/providers is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of @purest/providers 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 @purest/providers 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.

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
0 Direct
Versions
6
Install Size
64.2 kB
Dist-tags
1
# of Files
5
Maintainers
2
TS Typings
No

@purest/providers 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.