@akepinski/node-fetch

v3.0.0-beta.10

A light-weight module that brings window.fetch to node.js

MIT
Latest version published 2 years ago
    npm install @akepinski/node-fetch
  

Package Health Score

63 / 100

Popularity

Small

Weekly Downloads (2)

Download trend
Dependents
20.25K
GitHub Stars
6.99K
Forks
779
Contributors
80

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package @akepinski/node-fetch, we found that it has been starred 6,988 times, and that 20,251 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

04/2020

Direct Vulnerabilities

Popular
3.0.0-beta.10
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
3.0.0-beta.10
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
3.0.0-beta.10
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like @akepinski/node-fetch is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test @akepinski/node-fetch
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
130
Open PR
29
Last Release
2 years ago
Last Commit
15 days ago

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

Community

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

With more than 10 contributors for the @akepinski/node-fetch repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 63/100 package health 63/100

Package

Node.js Compatibility
>=10.0.0

Age
2 years
Dependencies
2 Direct
Versions
8
Install Size
115 kB
Dist-tags
1
# of Files
19
Maintainers
1
TS Typings
No

@akepinski/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.