Is @pelevesque/canonicalize-string safe to use?

@pelevesque/canonicalize-string has no known vulnerabilities on the latest version (0.0.6). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @pelevesque/canonicalize-string?

The latest version of @pelevesque/canonicalize-string is 0.0.6, released 2020-02-12.

Does @pelevesque/canonicalize-string have known vulnerabilities?

No known vulnerabilities on the latest version of @pelevesque/canonicalize-string.

Is @pelevesque/canonicalize-string deprecated?

No, @pelevesque/canonicalize-string is actively maintained. Latest release: 0.0.6 (2020-02-12).

What are alternatives to @pelevesque/canonicalize-string?

Popular alternatives to @pelevesque/canonicalize-string in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @pelevesque/canonicalize-string use?

@pelevesque/canonicalize-string is licensed under MIT.

@pelevesque/canonicalize-string

npmv0.0.6

Canonicalizes a UTF-8 string.

License MITpermissive6 versions1 maintainers2 deps29 weekly dl

pelevesque/canonicalize-string

/ 100

Health

use with caution

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

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/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

Dependencies (2)

diacritics unhomoglyph

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pelevesque/canonicalize-string