billing

v1.0.2

Billing Module Js

MIT
Latest version published about 4 years ago
    npm install billing
  

Package Health Score

45 / 100
  • Popularity
    Limited
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited
Make sure the open source you're using is safe to use Secure my Project

Popularity

Limited
Weekly Downloads (54)
Dependents
0
GitHub Stars
4
Forks
1
Contributors
1

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

Based on project statistics from the GitHub repository for the npm package billing, we found that it has been starred 4 times, and that 0 other projects on 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
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.7
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.7
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.7
1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

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 billing is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test billing
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
1
Merged PR
3
Open PR
0
Last Commit
4 years ago

Further analysis of the maintenance status of billing 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 billing 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
1
Funding
No
License
MIT

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct / 0 Total
Versions
2
Install Size
0 B
Dist-tags
3
# of Files
0
Maintainers
1
TS Typings
No

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