toxy

v0.3.16

Hackable HTTP proxy to simulate server failure scenarios and network conditions

MIT
Latest version published 4 years ago
    npm install toxy
  

Package Health Score

50 / 100

Security

No known security issues
Powered by Snyk
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.3.16 | 11/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.2.2 | 08/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.3 | 08/2015
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test toxy
Get started free

Popularity

Recognized

Weekly Downloads (1,261)

Download trend
Dependents
8
GitHub Stars
2.71K
Forks
101
Contributors
10

Direct Usage Popularity

Uncommon

The npm package toxy receives a total of 1,261 downloads a week. As such, we scored toxy popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package toxy, we found that it has been starred 2,711 times, and that 8 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.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
10
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Maintenance

Inactive

Commit Frequency

Open Issues
12
Open PR
2
Last Release
4 years ago
Last Commit
5 months ago

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

Package

Node.js Compatibility
>= 4

Age
7 years
Dependencies
6 Direct
Versions
26
Install Size
168 kB
Dist-tags
1
# of Files
115
Maintainers
1
TS Typings
No

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