whistle-extend

v0.0.11

HTTP, HTTP2, HTTPS, Websocket debugging proxy For more information about how to use this package see README

Latest version published 4 years 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

47 / 100

Security

Security review needed
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
0.0.11 | 04/2021
Popular
  • 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

Small

Weekly Downloads (1)

Download trend
GitHub Stars
14.36K
Forks
1.08K
Contributors
40

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package whistle-extend, we found that it has been starred 14,356 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
40
Funding
No

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


Embed Package Health Score Badge

package health: 47/100 package health 47/100

Maintenance

Inactive

Commit Frequency

Open Issues
43
Open PR
16
Last Release
4 years ago
Last Commit
29 days ago

Further analysis of the maintenance status of whistle-extend 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 whistle-extend 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
>= 6

Age
4 years
Dependencies
30 Direct
Versions
11
Install Size
2.47 MB
Dist-tags
1
# of Files
159
Maintainers
1
TS Typings
Yes

whistle-extend 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.