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.

Does number-to-locale-string-polyfill have known vulnerabilities?

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

Is number-to-locale-string-polyfill deprecated?

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

What are alternatives to number-to-locale-string-polyfill?

Popular alternatives to number-to-locale-string-polyfill in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does number-to-locale-string-polyfill use?

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

number-to-locale-string-polyfill

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,061 weekly dl

Girish-K/polyfill-Number.toLocaleString-with-Locales

/ 100

Health

use with caution

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

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

2/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/number-to-locale-string-polyfill