humanize-string 2.1.0
Convert a camelized/dasherized/underscored string into a humanized one: `fooBar-Baz_Faz` → `Foo bar baz faz`
humanize-string@2.1.0 was published on 2019-04-01. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All humanize-string versions · Permanent reference to 2.1.0 · Latest release
Package specifications
| Version | 2.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-04-01T09:41:23.831Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 3.71 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 112 |
| Repository forks | 12 |
Install humanize-string 2.1.0
npm install humanize-string@2.1.0 pnpm add humanize-string@2.1.0 yarn add humanize-string@2.1.0
Runtime dependencies
- decamelize ^2.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- decamelize@2.0.0 — direct
- xregexp@4.0.0 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 1/10 — Found 4/22 approved changesets -- score normalized to 1 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 10/10 — security policy file detected |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/humanize-string/2.1.0 — retrieved 2026-10-29T12:27:49.424Z
- https://api.deps.dev/v3/systems/npm/packages/humanize-string/versions/2.1.0:dependencies — retrieved 2026-10-29T12:27:50.014Z
- https://api.deps.dev/v3/systems/npm/packages/humanize-string/versions/2.1.0 — retrieved 2026-10-29T12:27:50.038Z
- https://api.deps.dev/v3/projects/github.com%2Fsindresorhus%2Fhumanize-string — retrieved 2026-10-29T12:27:50.623Z