npmpackage.info

Gathering detailed insights and metrics for @stdlib/fs-resolve-parent-path-cli

Gathering detailed insights and metrics for @stdlib/fs-resolve-parent-path-cli

@stdlib/fs-resolve-parent-path-cli - 0.2.2 | npmpackage.info

@stdlib/fs-resolve-parent-path-cli

Resolve a path by walking parent directories.

0.2.2

2

Apache-2.0

JavaScript

19.87 kB

Installations

npm install @stdlib/fs-resolve-parent-path-cli

Developer Guide

BETA

Typescript

No

Module System

N/A

Node Version

20.15.1

NPM Version

10.7.0

Score

61.2

Supply Chain

80.2

Quality

81.3

Maintenance

100

Vulnerability

88

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

1

JavaScript

JavaScript (100%)

Developer

Download Statistics

Total Downloads

711

Last Day

1

Last Week

5

Last Month

29

Last Year

318

GitHub Statistics

Apache-2.0 License

2 Stars

70 Commits

3 Watchers

6 Branches

13 Contributors

Updated on Apr 07, 2025

Sponsor this package

https://opencollective.com/stdlib

Maintainers

4

View All 13 Contributors

Package Meta Information

Latest Version

0.2.2

Package Id

@stdlib/fs-resolve-parent-path-cli@0.2.2

Unpacked Size

19.87 kB

Size

6.83 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

711

Last Day

-50%

1

Compared to previous day

Last Week

-54.5%

5

Compared to previous week

Last Month

16%

29

Compared to previous month

Last Year

-19.1%

318

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

3

@stdlib/cli-ctor @stdlib/fs-read-file @stdlib/fs-resolve-parent-path

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!

Resolve Parent Path

Resolve a path by walking parent directories.

Installation

To use as a general utility, install the CLI package globally

1npm install -g @stdlib/fs-resolve-parent-path-cli

Usage

1Usage: resolve-parent-path [options] <path>
2
3Options:
4
5  -h,    --help                Print this message.
6  -V,    --version             Print the package version.
7         --dir dir             Base search directory.

Examples

1$ resolve-parent-path package.json

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

Copyright

Copyright © 2016-2024. The Stdlib Authors.

Empty State

No vulnerabilities found.

10

Binary-Artifacts

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

10

License

Determines if the project has defined a license.

10

Dangerous-Workflow

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

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

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:274: update your workflow using https://app.stepsecurity.io/secureworkflow/stdlib-js/fs-resolve-parent-path/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/fs-resolve-parent-path/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/fs-resolve-parent-path/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/fs-resolve-parent-path/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/fs-resolve-parent-path/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: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/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/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

1

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

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

0

Code-Review

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

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.3

/10

Last Scanned on 2025-05-05

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.