zipkin-instrumentation-fetch

v0.22.0

Interceptor for HTTP clients using the 'fetch' API For more information about how to use this package see README

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

53 / 100

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
0.22.0 | 06/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.21.0 | 04/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.20.0 | 03/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.19.2 | 02/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.18.6 | 07/2019
  • 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

Recognized

Weekly Downloads (17,234)

Download trend
GitHub Stars
561
Forks
173
Contributors
80

Direct Usage Popularity

TOP 5%

The npm package zipkin-instrumentation-fetch receives a total of 17,234 downloads a week. As such, we scored zipkin-instrumentation-fetch popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package zipkin-instrumentation-fetch, we found that it has been starred 561 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
80
Funding
No

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of zipkin-instrumentation-fetch 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 zipkin-instrumentation-fetch 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
not defined

Age
8 years
Dependencies
1 Direct
Versions
59
Install Size
15.4 kB
Dist-tags
2
# of Files
10
Maintainers
1
TS Typings
Yes

zipkin-instrumentation-fetch 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.