@aspida/node-fetch

v1.14.0

node-fetch client for aspida 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

61 / 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
1.14.0 | 08/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.13.3 | 08/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.9.2 | 11/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.8.4 | 09/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.7.2 | 08/2020
  • 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 (187)

Download trend
GitHub Stars
1.07K
Forks
35
Contributors
20

Direct Usage Popularity


The npm package @aspida/node-fetch receives a total of 187 downloads a week. As such, we scored @aspida/node-fetch popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @aspida/node-fetch, we found that it has been starred 1,070 times.

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

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the @aspida/node-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 @aspida/node-fetch is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 61/100 package health 61/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
11
Open PR
8
Last Release
1 year ago
Last Commit
1 year ago

Further analysis of the maintenance status of @aspida/node-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 @aspida/node-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.

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
not defined

Age
5 years
Dependencies
0 Direct
Versions
58
Install Size
16.3 kB
Dist-tags
1
# of Files
11
Maintainers
2
TS Typings
No

@aspida/node-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.