Is @jimpick/w3c-keyname safe to use?

@jimpick/w3c-keyname has no known vulnerabilities on the latest version (2.1.0-2). DepScope rates its health at 40/100 (high risk).

What is the latest version of @jimpick/w3c-keyname?

The latest version of @jimpick/w3c-keyname is 2.1.0-2, released 2018-11-04.

Does @jimpick/w3c-keyname have known vulnerabilities?

No known vulnerabilities on the latest version of @jimpick/w3c-keyname.

Is @jimpick/w3c-keyname deprecated?

No, @jimpick/w3c-keyname is actively maintained. Latest release: 2.1.0-2 (2018-11-04).

What are alternatives to @jimpick/w3c-keyname?

Popular alternatives to @jimpick/w3c-keyname in npm include: ?, semver, ansi-styles, minimatch, debug.

What license does @jimpick/w3c-keyname use?

@jimpick/w3c-keyname is licensed under MIT.

@jimpick/w3c-keyname

npmv2.1.0-2

Get a KeyboardEvent.key-style string from an event

License MITpermissive2 versions1 maintainers0 deps899 weekly dl

marijnh/w3c-keyname

/ 100

Health

use with caution

@jimpick/[email protected] low health (40/100) — consider alternatives

Moderate health score (40/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@jimpick/w3c-keyname