npmpackage.info

@stdlib/assert-is-node-builtin

Test whether a string matches a Node.js built-in module name.

0.2.2

Apache-2.0

JavaScript

3.61 kB

3,872 4.4

Installations

npm install @stdlib/assert-is-node-builtin

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>=0.10.0

Node Version

16.20.2

NPM Version

8.19.4 Score

65.8

Supply Chain

82.3

Quality

82.9

Maintenance

100

Vulnerability

87.6

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

View All 11 Contributors

Languages

JavaScript

JavaScript (100%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

stdlib-js

Download Statistics

Total Downloads

3,872

Last Day

Last Week

Last Month

Last Year

696

GitHub Statistics

Apache-2.0 License

2 Stars

66 Commits

3 Watchers

6 Branches

11 Contributors

Updated on Jan 06, 2025

Bundle Size

12.85 kB

Minified

3.61 kB

Minified + Gzipped

Bundlephobia

Sponsor this package

https://opencollective.com/stdlib

Maintainers

Package Meta Information

Latest Version

0.2.2

Package Id

@stdlib/assert-is-node-builtin@0.2.2

Unpacked Size

29.38 kB

Size

8.70 kB

File Count

NPM Version

8.19.4

Node Version

16.20.2

Published on

Jul 28, 2024

Total Downloads

Cumulative downloads

Total Downloads

3,872

Last Day

400%

Compared to previous day

Last Week

-36.4%

Compared to previous week

Last Month

36.4%

Compared to previous month

Last Year

-40.6%

696

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@stdlib/assert-contains @stdlib/assert-is-string

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

1npm install @stdlib/assert-is-node-builtin

Usage

1var isNodeBuiltin = require( '@stdlib/assert-is-node-builtin' );

isNodeBuiltin( value )

Tests whether a string matches a Node.js built-in module name.

1var bool = isNodeBuiltin( 'util' );
2// returns true

Notes

For non-string values, the function returns false.

Examples

1var isNodeBuiltin = require( '@stdlib/assert-is-node-builtin' );
2
3var out = isNodeBuiltin( 'fs' );
4// returns true
5
6out = isNodeBuiltin( 'child_process' );
7// returns true
8
9out = isNodeBuiltin( 'fs-extra' );
10// returns false
11
12out = isNodeBuiltin( 'moment' );
13// returns false

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

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

9

Security-Policy

Determines if the project has published a security policy.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

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: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/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/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

2

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

Score

4.4

/10

Last Scanned on 2025-02-03

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

Other packages similar to @stdlib/assert-is-node-builtin

@stdlib/assert-is-node-builtin-cli

0.2.2

Test whether a string matches a Node.js built-in module name.

@stdlib/assert-is-node-builtin

Installations

Developer Guide

Yes

CommonJS

>=0.10.0

16.20.2

8.19.4

Score

Pull Requests

0

0

0

Issues

0

0

0

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

Languages

Developer

Download Statistics

GitHub Statistics

Bundle Size

12.85 kB

3.61 kB

Sponsor this package

Maintainers

Package Meta Information

Total Downloads

3,872

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

isNodeBuiltin

Installation

Usage

isNodeBuiltin( value )

Notes

Examples

See Also

Notice

Community

License

Copyright

10

10

10

10

9

3

2

0

0

0

0

0

0

4.4

/10

Other packages similar to @stdlib/assert-is-node-builtin