Installations
npm install @stdlib/string-truncate-cliDeveloper Guide
Typescript
No
Module System
N/A
Node Version
20.15.1
NPM Version
10.7.0
Score
56.7
Supply Chain
68.1
Quality
81.2
Maintenance
100
Vulnerability
87.6
License
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
validate.email 🚀
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Developer
Download Statistics
Total Downloads
499
Last Day
1
Last Week
1
Last Month
5
Last Year
217
GitHub Statistics
Apache-2.0 License
3 Stars
60 Commits
3 Watchers
6 Branches
12 Contributors
Updated on Mar 17, 2025
Sponsor this package
Maintainers
Package Meta Information
Latest Version
0.2.2
Package Id
@stdlib/string-truncate-cli@0.2.2
Unpacked Size
23.07 kB
Size
7.64 kB
File Count
7
NPM Version
10.7.0
Node Version
20.15.1
Published on
Jul 27, 2024
Total Downloads
Cumulative downloads
Total Downloads
499
Last Day
0%
1
Compared to previous day
Last Week
0%
1
Compared to previous week
Last Month
-82.1%
5
Compared to previous month
Last Year
-23%
217
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
About stdlib...
We believe in a future in which the web is a preferred environment for numerical computation. To help realize this future, we've built stdlib. stdlib is a standard library, with an emphasis on numerical and scientific computation, written in JavaScript (and C) for execution in browsers and in Node.js.
The library is fully decomposable, being architected in such a way that you can swap out and mix and match APIs and functionality to cater to your exact preferences and use cases.
When you use stdlib, you can be absolutely certain that you are using the most thorough, rigorous, well-written, studied, documented, tested, measured, and high-quality code out there.
To join us in bringing numerical computing to the web, get started by checking us out on GitHub, and please consider financially supporting stdlib. We greatly appreciate your continued support!
truncate
Truncate a string to a specified length.
Installation
To use as a general utility, install the CLI package globally
1npm install -g @stdlib/string-truncate-cli
Usage
1Usage: truncate [options] [<string>] --len <length> 2 3Options: 4 5 -h, --help Print this message. 6 -V, --version Print the package version. 7 --len length String length. 8 --ending str Custom ending. Default: '...'. 9 --split sep Delimiter for stdin data. Default: '/\\r?\\n/'.
Notes
-
If the split separator is a regular expression, ensure that the
splitoption is either properly escaped or enclosed in quotes.1# Not escaped... 2$ echo -n $'Hello, World!\nBeep Boop Baz' | truncate --len 6 --split /\r?\n/ 3 4# Escaped... 5$ echo -n $'Hello, World!\nBeep Boop Baz' | truncate --len 6 --split /\\r?\\n/ -
The implementation ignores trailing delimiters.
Examples
1$ truncate 'Hello, World!' --len 8 2Hello... 3 4$ truncate 'Hello, World!' --len 6 --ending '!' 5Hello!
To use as a standard stream,
1$ echo -n 'Hello, World!' | truncate --len 8 2Hello...
By default, when used as a standard stream, the implementation assumes newline-delimited data. To specify an alternative delimiter, set the split option.
1$ echo -n 'Hello, World!\tBeep Boop' | truncate --split '\t' --len 8 2Hello... 3Beep ...
See Also
@stdlib/string-truncate: truncate a string to a specified length.@stdlib/string-truncate-cli-middle: truncate a string in the middle to a specified length.
Notice
This package is part of stdlib, a standard library for JavaScript and Node.js, with an emphasis on numerical and scientific computing. The library provides a collection of robust, high performance libraries for mathematics, statistics, streams, utilities, and more.
For more information on the project, filing bug reports and feature requests, and guidance on how to develop stdlib, see the main project repository.
Community
License
See LICENSE.
Copyright
Copyright © 2016-2024. The Stdlib Authors.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: Apache License 2.0: LICENSE:0
Reason
security policy file detected
Details
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy
- Info: Found text in security policy: SECURITY.md:1
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:274: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/string-truncate/productionize.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:448: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/string-truncate/productionize.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:456: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/string-truncate/productionize.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:621: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/string-truncate/productionize.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:84: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/string-truncate/productionize.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/examples.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/examples.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/examples.yml:58
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:156
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:156
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:156
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:164
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:268
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:268
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:268
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:435
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:435
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:435
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:615
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:615
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:615
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:794
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:794
- Warn: npmCommand not pinned by hash: .github/workflows/productionize.yml:794
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:76
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:76
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:76
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:83
- Warn: npmCommand not pinned by hash: .github/workflows/test_bundles.yml:72
- Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:67
- Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:67
- Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:67
- Warn: npmCommand not pinned by hash: .github/workflows/test_coverage.yml:74
- Warn: npmCommand not pinned by hash: .github/workflows/test_install.yml:75
- Warn: npmCommand not pinned by hash: .github/workflows/test_install.yml:75
- Warn: npmCommand not pinned by hash: .github/workflows/test_install.yml:75
- Warn: npmCommand not pinned by hash: .github/workflows/test_published_package.yml:93
- Info: 37 out of 37 GitHub-owned GitHubAction dependencies pinned
- Info: 23 out of 28 third-party GitHubAction dependencies pinned
- Info: 0 out of 35 npmCommand dependencies pinned
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/benchmark.yml:1
- Warn: no topLevel permission defined: .github/workflows/cancel.yml:1
- Warn: no topLevel permission defined: .github/workflows/close_pull_requests.yml:1
- Warn: no topLevel permission defined: .github/workflows/examples.yml:1
- Warn: no topLevel permission defined: .github/workflows/npm_downloads.yml:1
- Warn: no topLevel permission defined: .github/workflows/productionize.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish_cli.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Warn: no topLevel permission defined: .github/workflows/test_bundles.yml:1
- Warn: no topLevel permission defined: .github/workflows/test_coverage.yml:1
- Warn: no topLevel permission defined: .github/workflows/test_install.yml:1
- Warn: no topLevel permission defined: .github/workflows/test_published_package.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Score
4.2
/10
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More