recurring

v2.7.0

a recurly v2 api client for node.js

MIT
Latest version published 3 years ago
    npm install recurring
  

Package Health Score

43 / 100

Popularity

Limited

Weekly Downloads (400)

Download trend
Dependents
0
GitHub Stars
30
Forks
41
Contributors
20

Direct Usage Popularity

Occasionally

The npm package recurring receives a total of 400 downloads a week. As such, we scored recurring popularity level to be Limited.

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

02/2014
06/2014
10/2014
03/2018
03/2018

Direct Vulnerabilities

0.0.8
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.3.8
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.7.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

0.0.8
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0
  • 0
    H
  • 0
    M
  • 0
    L
2.3.8
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.7.0
  • 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 recurring 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 recurring
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
11
Open PR
9
Last Release
3 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of recurring 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 recurring 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
20
Funding
No

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


Embed Package Health Score Badge

package health: 43/100 package health 43/100

Package

Node.js Compatibility
not defined

Age
9 years
Dependencies
10 Direct
Versions
37
Install Size
129 kB
Dist-tags
3
# of Files
40
Maintainers
2
TS Typings
No

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