Is use-fetched-state safe to use?

use-fetched-state has no known vulnerabilities on the latest version (2.37.0). DepScope rates its health at 41/100 (high risk).

What is the latest version of use-fetched-state?

The latest version of use-fetched-state is 2.37.0, released 2024-11-16.

Does use-fetched-state have known vulnerabilities?

No known vulnerabilities on the latest version of use-fetched-state.

Is use-fetched-state deprecated?

No, use-fetched-state is actively maintained. Latest release: 2.37.0 (2024-11-16).

What are alternatives to use-fetched-state?

Popular alternatives to use-fetched-state in npm include: ?, semver, ansi-styles, minimatch, debug.

What license does use-fetched-state use?

use-fetched-state is licensed under MIT.

use-fetched-state

npmv2.37.0

A simple yet convenient `fetch` + `useState` wrapper. 100% TS. Less than 100 LOC. 0 dependencies.

License MITpermissive18 versions1 maintainers0 deps21 weekly dl

kiprasmel/turbo-schedule

/ 100

Health

use with caution

[email protected] low health (41/100) — consider alternatives

Moderate health score (41/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

4.3 KBminified

1.8 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/use-fetched-state