Installations
npm install @supercharge/stringsDeveloper Guide
Typescript
Yes
Module System
CommonJS
Node Version
16.19.0
NPM Version
9.2.0
Score
99.2
Supply Chain
94.4
Quality
80
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (50.04%)
TypeScript (49.96%)
Developer
Download Statistics
Total Downloads
3,427,222
Last Day
5,732
Last Week
32,799
Last Month
161,857
Last Year
2,064,136
GitHub Statistics
44 Stars
408 Commits
18 Forks
4 Watching
1 Branches
11 Contributors
Bundle Size
16.85 kB
Minified
5.75 kB
Minified + Gzipped
Maintainers
Package Meta Information
Latest Version
2.0.0
Package Id
@supercharge/strings@2.0.0
Unpacked Size
59.60 kB
Size
11.79 kB
File Count
19
NPM Version
9.2.0
Node Version
16.19.0
Total Downloads
Cumulative downloads
Total Downloads
3,427,222
Last day
-6.6%
5,732
Compared to previous day
Last week
-15.2%
32,799
Compared to previous week
Last month
-4.8%
161,857
Compared to previous month
Last year
173.5%
2,064,136
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Strings
String utilities for Node.js.
Installation · Docs · Usage
Follow @marcuspoehls and @superchargejs for updates!
Introduction
The @supercharge/strings package provides chainable string utilities for Node.js and JavaScript. It’s a wrapper around JavaScript’s global String class providing a handful of useful methods, like .title(), .strip(), .camel(), and so on.
Installation
npm i @supercharge/strings
Docs
Find all the details for @supercharge/strings in the extensive Supercharge docs.
Usage
Using @supercharge/strings is pretty straightforward. Pass a string to the imported Function and chain your desired methods to transform to string value to your needs.
For example, you may want to trim a string and then title-case it:
1const Str = require('@supercharge/strings') 2 3const title = Str(' Supercharge is sweet!').trim().title().get() 4 5// title: "Supercharge Is Sweet!"
For every method in the chain that would return a string, the package returns an instance of iteself. This way, you can chain further methods. Call .get() to retrieve the actual JavaScript string.
Contributing
Do you miss a string function? We very much appreciate your contribution! Please send in a pull request 😊
- Create a fork
- Create your feature branch:
git checkout -b my-feature - Commit your changes:
git commit -am 'Add some feature' - Push to the branch:
git push origin my-new-feature - Submit a pull request 🚀
License
MIT © Supercharge
superchargejs.com  · GitHub @supercharge  · Twitter @superchargejs
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: MIT License: LICENSE:0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/11 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/publish-in-github-package-registry.yml:1
- Warn: no topLevel permission defined: .github/workflows/run-tests.yml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/publish-in-github-package-registry.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/publish-in-github-package-registry.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/publish-in-github-package-registry.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/publish-in-github-package-registry.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/publish-in-github-package-registry.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/run-tests.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/run-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/run-tests.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/run-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/run-tests.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/supercharge/strings/run-tests.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:20
- Warn: npmCommand not pinned by hash: .github/workflows/publish-in-github-package-registry.yml:38
- Warn: npmCommand not pinned by hash: .github/workflows/run-tests.yml:37
- Info: 0 out of 8 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 20 are checked with a SAST tool
Score
3.4
/10
Last Scanned on 2025-01-27
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