Is @descope-ui/descope-country-subdivision-city-field safe to use?

@descope-ui/descope-country-subdivision-city-field has no known vulnerabilities on the latest version (3.3.5). DepScope rates its health at 71/100 (moderate risk).

Does @descope-ui/descope-country-subdivision-city-field have known vulnerabilities?

No known vulnerabilities on the latest version of @descope-ui/descope-country-subdivision-city-field.

Is @descope-ui/descope-country-subdivision-city-field deprecated?

No, @descope-ui/descope-country-subdivision-city-field is actively maintained. Latest release: 3.3.5 (2026-05-06).

What are alternatives to @descope-ui/descope-country-subdivision-city-field?

Popular alternatives to @descope-ui/descope-country-subdivision-city-field in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @descope-ui/descope-country-subdivision-city-field use?

License information for @descope-ui/descope-country-subdivision-city-field is not declared in the registry metadata.

@descope-ui/descope-country-subdivision-city-field

npmv3.3.5

27 versions2 maintainers4 deps3,869 weekly dl

71

/ 100

Health

safe to use

@descope-ui/[email protected] is safe to use (health: 71/100)

Health breakdown0 – 100

25/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

0

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

@vaadin/custom-field @descope-ui/common @descope-ui/theme-input-wrapper @descope-ui/descope-combo-box

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@descope-ui/descope-country-subdivision-city-field