bproxy

v5.2.36

代理工具 For more information about how to use this package see README

Latest version published 1 year 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

46 / 100

Explore Similar Packages

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
5.2.36 | 12/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.2.24 | 03/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.1.2 | 05/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.9 | 05/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.23 | 11/2019
  • 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 (2)

Download trend
GitHub Stars
282
Forks
13
Contributors
2

Direct Usage Popularity


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

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 46/100 package health 46/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
1
Last Release
1 year ago
Last Commit
4 months ago

Further analysis of the maintenance status of bproxy 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 bproxy 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
>= 16.0.0

Age
8 years
Dependencies
12 Direct
Versions
109
Install Size
9.8 MB
Dist-tags
1
# of Files
1.21K
Maintainers
1
TS Typings
No

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