1. Advisor
  2. JavaScript packages
  3. use-force-update

use-force-update

v1.0.11

React Hook to force your function component to update. For more information about how to use this package see README

Latest version published 2 years ago
License: MIT
NPM
GitHub

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

50 / 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.0.11 | 11/2022
Popular
  • 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

Recognized

Weekly Downloads (19,533)

Download trend
GitHub Stars
183
Forks
11
Contributors
5

Direct Usage Popularity

TOP 5%

The npm package use-force-update receives a total of 19,533 downloads a week. As such, we scored use-force-update popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package use-force-update, we found that it has been starred 183 times.

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

Community

Limited
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
5
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like use-force-update is missing a Code of Conduct.

How about a good first contribution to this project? It seems that use-force-update is missing a README file.

Embed Package Health Score Badge

package health: 50/100 package health 50/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
2 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of use-force-update 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 use-force-update 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.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
6 years
Dependencies
0 Direct
Versions
13
Install Size
9.65 kB
Dist-tags
1
# of Files
6
Maintainers
1
TS Typings
Yes

use-force-update 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.