Installations
npm install @stdlib/assert-is-node-builtin-cliDeveloper Guide
Typescript
No
Module System
N/A
Node Version
20.15.1
NPM Version
10.7.0
Score
56.1
Supply Chain
71.8
Quality
81.9
Maintenance
100
Vulnerability
87.6
License
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
Download Statistics
Total Downloads
497
Last Day
1
Last Week
3
Last Month
27
Last Year
334
GitHub Statistics
Apache-2.0 License
2 Stars
66 Commits
3 Watchers
6 Branches
11 Contributors
Updated on Jan 06, 2025
Sponsor this package
Maintainers
Package Meta Information
Latest Version
0.2.2
Package Id
@stdlib/assert-is-node-builtin-cli@0.2.2
Unpacked Size
21.60 kB
Size
7.39 kB
File Count
7
NPM Version
10.7.0
Node Version
20.15.1
Published on
Jul 28, 2024
Total Downloads
Cumulative downloads
Total Downloads
497
Last Day
0%
1
Compared to previous day
Last Week
-57.1%
3
Compared to previous week
Last Month
68.8%
27
Compared to previous month
Last Year
104.9%
334
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!
isNodeBuiltin
Test whether a string matches a Node.js built-in module name.
Installation
To use as a general utility, install the CLI package globally
1npm install -g @stdlib/assert-is-node-builtin-cli
Usage
1Usage: is-node-builtin [options] [<string>] 2 3Options: 4 5 -h, --help Print this message. 6 -V, --version Print the package version. 7 --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 $'crypto\nndarray' | is-note-builtin --split /\r?\n/ 3# Escaped... 4$ echo -n $'crypto\nndarray' | is-note-builtin --split /\\r?\\n/ -
The implementation ignores trailing delimiters.
Examples
1$ is-node-builtin crypto 2true
To use as a standard stream,
1$ echo -n 'crypto\ncluster\nfs-extra' | is-node-builtin 2true 3true 4false
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 'crypto\tbaz' | is-node-builtin --split '\t' 2true 3false
See Also
@stdlib/assert-is-node-builtin: test whether a string matches a Node.js built-in module name.
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
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
no dangerous workflow patterns detected
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:84: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/assert-is-node-builtin/productionize.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/productionize.yml:274: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/assert-is-node-builtin/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/assert-is-node-builtin/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/assert-is-node-builtin/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/assert-is-node-builtin/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: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/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/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
3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
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
Score
4.4
/10
Last Scanned on 2025-02-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