@wessberg/stringutil 1.0.17
A collection of helper functions for working with strings
@wessberg/stringutil@1.0.17 was published on 2018-06-20. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=9.0.0.
All @wessberg/stringutil versions · Permanent reference to 1.0.17 · Latest release
Package specifications
| Version | 1.0.17 |
|---|---|
| License declaration | MIT |
| Published | 2018-06-20T20:31:39.951Z |
| Node.js requirement | >=9.0.0 |
| Type declarations | Bundled declarations |
| 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 | 46.12 KiB |
| Published file count | 15 |
| Package type | Not declared |
| ES module entry | ./dist/es2015/index.js |
| Default entry | ./dist/cjs/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 0 |
| Repository forks | 0 |
Install @wessberg/stringutil 1.0.17
npm install @wessberg/stringutil@1.0.17 pnpm add @wessberg/stringutil@1.0.17 yarn add @wessberg/stringutil@1.0.17
Runtime dependencies
- tslib ^1.9.2
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.
- tslib@1.14.1 — direct
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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not 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 |
Evidence and freshness
- https://registry.npmjs.org/%40wessberg%2Fstringutil/1.0.17 — retrieved 2026-10-29T11:13:38.113Z
- https://api.deps.dev/v3/projects/github.com%2Fwessberg%2Fstringutil — retrieved 2026-10-29T07:16:00.316Z
- https://api.deps.dev/v3/systems/npm/packages/%40wessberg%2Fstringutil/versions/1.0.17 — retrieved 2026-10-29T11:13:38.650Z
- https://api.deps.dev/v3/systems/npm/packages/%40wessberg%2Fstringutil/versions/1.0.17:dependencies — retrieved 2026-10-29T11:13:38.684Z