Is number-to-locale-string-polyfill safe to use?

number-to-locale-string-polyfill has no known vulnerabilities on the latest version (1.0.9). DepScope rates its health at 45/100 (high risk).

What is the latest version of number-to-locale-string-polyfill?

The latest version of number-to-locale-string-polyfill is 1.0.9, released 2019-01-06.

No known vulnerabilities on the latest version of number-to-locale-string-polyfill.

No, number-to-locale-string-polyfill is actively maintained. Latest release: 1.0.9 (2019-01-06).

Popular alternatives to number-to-locale-string-polyfill in npm include: minimatch, chalk, commander, picomatch, eslint-visitor-keys.

number-to-locale-string-polyfill is licensed under UNLICENSED.

npmv1.0.9

A polyfill to add support for Number.toLocaleString with locales to browsers that don't support it.

License UNLICENSEDproprietary5 versions1 maintainers0 deps1,045 weekly dl

/ 100

Health

safe to use

[email protected] is safe to use (health: 45/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

🌟

0/10untyped

No type definitions available

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/number-to-locale-string-polyfill