paid-services

v6.1.4

Lightning Paid Services library For more information about how to use this package see README

Latest version published 5 days ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

60 / 100

Explore Similar Packages

Security

No known security issues
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
6.1.4 | 06/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.0 | 03/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.5 | 10/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.3.5 | 03/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.2.2 | 01/2023
  • 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.

Get started free

Popularity

Limited

Weekly Downloads (350)

Download trend
GitHub Stars
7
Forks
3
Contributors
3

Direct Usage Popularity

Uncommon

The npm package paid-services receives a total of 350 downloads a week. As such, we scored paid-services popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package paid-services, we found that it has been starred 7 times.

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
3
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 60/100 package health 60/100

Maintenance

Sustainable

Commit Frequency

Open Issues
0
Open PR
0
Last Release
5 days ago
Last Commit
16 days ago

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

We found that paid-services demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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

Age
3 years
Dependencies
15 Direct
Versions
89
Install Size
991 kB
Dist-tags
1
# of Files
303
Maintainers
1
TS Typings
No

paid-services 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.