Is humanize-string safe to use?

humanize-string has no known vulnerabilities on the latest version (3.1.0). DepScope rates its health at 66/100 (moderate risk).

What is the latest version of humanize-string?

The latest version of humanize-string is 3.1.0, released 2025-09-12.

Does humanize-string have known vulnerabilities?

No known vulnerabilities on the latest version of humanize-string.

Is humanize-string deprecated?

No, humanize-string is actively maintained. Latest release: 3.1.0 (2025-09-12).

What are alternatives to humanize-string?

Popular alternatives to humanize-string in npm include: semver, ansi-styles, strip-ansi, ms, lru-cache.

What license does humanize-string use?

humanize-string is licensed under MIT.

humanize-string

npmv3.1.0

Convert a camelized/dasherized/underscored string into a humanized one: `fooBar-Baz_Faz` → `Foo bar baz faz`

License MITpermissive7 versions1 maintainers1 deps571,330 weekly dl

sindresorhus/humanize-string

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

14/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.1 KBminified

0.5 KB gzipped

1 direct dependencies

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

decamelize

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/humanize-string