Is is-valid-element-name safe to use?

is-valid-element-name has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 39/100 (critical risk).

What is the latest version of is-valid-element-name?

The latest version of is-valid-element-name is 1.0.0, released 2016-06-22.

Does is-valid-element-name have known vulnerabilities?

No known vulnerabilities on the latest version of is-valid-element-name.

Is is-valid-element-name deprecated?

No, is-valid-element-name is actively maintained. Latest release: 1.0.0 (2016-06-22).

What are alternatives to is-valid-element-name?

Popular alternatives to is-valid-element-name in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does is-valid-element-name use?

is-valid-element-name is licensed under BSD-2-Clause.

is-valid-element-name

npmv1.0.0

Validates custom element names according to the custom elements spec

License BSD-2-Clausepermissive1 versions1 maintainers1 deps

matthewp/is-valid-element-name

/ 100

Health

use with caution

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

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.8 KBminified

0.4 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

is-potential-custom-element-name

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/is-valid-element-name