wreck

v14.2.0

HTTP Client Utilities For more information about how to use this package see README

Latest version published 4 years ago
License: BSD-3-Clause

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

58 / 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
14.2.0 | 03/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
14.1.4 | 02/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
13.0.3 | 09/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
12.5.1 | 09/2017
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
12.4.0 | 09/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
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

Popular

Weekly Downloads (136,694)

Download trend
Dependents
92
GitHub Stars
383
Forks
107
Contributors
50

Direct Usage Popularity

TOP 10%

The npm package wreck receives a total of 136,694 downloads a week. As such, we scored wreck popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package wreck, we found that it has been starred 383 times, and that 92 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

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

With more than 10 contributors for the wreck repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
2
Last Release
4 years ago
Last Commit
7 months ago

Further analysis of the maintenance status of wreck 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 wreck 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
3 Direct
Versions
53
Install Size
42.2 kB
Dist-tags
1
# of Files
9
Maintainers
1
TS Typings
Yes

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