Is use-optionally-controlled-state safe to use?

use-optionally-controlled-state has no known vulnerabilities on the latest version (1.2.0). DepScope rates its health at 22/100 (critical risk).

What is the latest version of use-optionally-controlled-state?

The latest version of use-optionally-controlled-state is 1.2.0, released 2022-05-11.

Does use-optionally-controlled-state have known vulnerabilities?

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

Is use-optionally-controlled-state deprecated?

Yes, use-optionally-controlled-state is deprecated: This package was renamed to `use-optional-state`, please use the new package instead: https://www.npmjs.com/package/use-optional-state Consider using ? instead.

What are alternatives to use-optionally-controlled-state?

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

What license does use-optionally-controlled-state use?

use-optionally-controlled-state is licensed under MIT.

use-optionally-controlled-state

npmv1.2.0deprecated

A React hook to implement components that support both controlled and uncontrolled props.

License MITpermissive8 versions1 maintainers2 deps195 weekly dl

amannn/react-hooks

/ 100

Health

find alternative

use-optionally-controlled-state is deprecated — find an alternative

Moderate health score (22/100) — verify manually
Package is deprecated

Health breakdown0 – 100

10/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

tslib use-constant

API access

Get this data programmatically — free, no authentication.

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