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

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

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

The latest version of number-to-locale-string is 1.2.0, released 2017-12-21.

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

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

Is number-to-locale-string deprecated?

No, number-to-locale-string is actively maintained. Latest release: 1.2.0 (2017-12-21).

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

Popular alternatives to number-to-locale-string in npm include: semver, debug, minimatch, strip-ansi, lru-cache.

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

number-to-locale-string is licensed under Public Domain.

number-to-locale-string

npmv1.2.0

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

License Public Domain4 versions1 maintainers0 deps2,993 weekly dl

willsp/polyfill-Number.toLocaleString-with-Locales

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

2.9 KBminified

1.4 KB gzipped

0 direct dependencies

side effects

🌟

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