transfer-rate

v2.2.0

calculate transfer-rate of request/response For more information about how to use this package see README

Latest version published 6 years ago
License: Apache-2.0

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

48 / 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
2.2.0 | 12/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.1.0 | 05/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0 | 09/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 08/2014
  • 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.

Get started free

Popularity

Small

Weekly Downloads (1,023)

Download trend
GitHub Stars
6
Forks
4
Contributors
1

Direct Usage Popularity

Uncommon

The npm package transfer-rate receives a total of 1,023 downloads a week. As such, we scored transfer-rate popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package transfer-rate, we found that it has been starred 6 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
1
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
7
Last Release
6 years ago
Last Commit
6 years ago

Further analysis of the maintenance status of transfer-rate 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 transfer-rate 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=4

Age
10 years
Dependencies
1 Direct
Versions
18
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

transfer-rate 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.