@types/npm-registry-fetch

v8.0.7

TypeScript definitions for npm-registry-fetch 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

66 / 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
4.0.7 | 11/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.0.7 | 11/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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 (39,924)

Download trend
GitHub Stars
48.72K
Forks
30.19K
Contributors
-

Direct Usage Popularity

Uncommon

The npm package @types/npm-registry-fetch receives a total of 39,924 downloads a week. As such, we scored @types/npm-registry-fetch popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @types/npm-registry-fetch, we found that it has been starred 48,720 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
0
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like @types/npm-registry-fetch is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 66/100 package health 66/100

Maintenance

Inactive

Commit Frequency

Open Issues
555
Open PR
152
Last Release
1 year ago
Last Commit
29 days ago

Further analysis of the maintenance status of @types/npm-registry-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 @types/npm-registry-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
5 Direct
Versions
17
Install Size
19.4 kB
Dist-tags
30
# of Files
5
Maintainers
1
TS Typings
No

@types/npm-registry-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.