Gathering detailed insights and metrics for resolve-from
Gathering detailed insights and metrics for resolve-from
Resolve the path of a module like require.resolve() but from a given path
Installations
npm install resolve-fromDeveloper
sindresorhus
Developer Guide
BETA
Module System
Unable to determine the module system for this package.
Min. Node Version
>=8
Typescript Support
No
Node Version
8.15.0
NPM Version
6.9.0
Statistics
140 Stars
30 Commits
13 Forks
7 Watching
1 Branches
7 Contributors
Updated on 15 Nov 2024
Bundle Size
841.00 B
Minified
435.00 B
Minified + Gzipped
Languages
JavaScript (92.73%)
TypeScript (7.27%)
Total Downloads
Cumulative downloads
Total Downloads
15,969,123,891
Last day
-7.5%
17,347,745
Compared to previous day
Last week
0.7%
101,624,939
Compared to previous week
Last month
14.3%
416,268,853
Compared to previous month
Last year
12.8%
4,192,843,221
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Versions
resolve-from
Resolve the path of a module like
require.resolve()but from a given path
Install
$ npm install resolve-from
Usage
1const resolveFrom = require('resolve-from'); 2 3// There is a file at `./foo/bar.js` 4 5resolveFrom('foo', './bar'); 6//=> '/Users/sindresorhus/dev/test/foo/bar.js'
API
resolveFrom(fromDirectory, moduleId)
Like require(), throws when the module can't be found.
resolveFrom.silent(fromDirectory, moduleId)
Returns undefined instead of throwing when the module can't be found.
fromDirectory
Type: string
Directory to resolve from.
moduleId
Type: string
What you would use in require().
Tip
Create a partial using a bound function if you want to resolve from the same fromDirectory multiple times:
1const resolveFromFoo = resolveFrom.bind(null, 'foo'); 2 3resolveFromFoo('./bar'); 4resolveFromFoo('./baz');
resolve-from for enterprise
Available as part of the Tidelift Subscription.
The maintainers of resolve-from and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.
Related
- resolve-cwd - Resolve the path of a module from the current working directory
- import-from - Import a module from a given path
- import-cwd - Import a module from the current working directory
- resolve-pkg - Resolve the path of a package regardless of it having an entry point
- import-lazy - Import a module lazily
- resolve-global - Resolve the path of a globally installed module
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
security policy file detected
Details
- Info: security policy file detected: .github/security.md:1
- Info: Found linked content: .github/security.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: .github/security.md:1
- Info: Found text in security policy: .github/security.md:1
Reason
no dangerous workflow patterns 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 existing vulnerabilities detected
Reason
Found 7/30 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/resolve-from/main.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/resolve-from/main.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/main.yml:23
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/main.yml:1
- Info: no jobLevel write permissions found
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
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 7 are checked with a SAST tool
Score
4.2
/10
Last Scanned on 2024-11-18
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