Gathering detailed insights and metrics for p-locate
Gathering detailed insights and metrics for p-locate
Get the first fulfilled promise that satisfies the provided testing function
Installations
npm install p-locateDeveloper Guide
BETA
Typescript
No
Module System
ESM
Min. Node Version
^12.20.0 || ^14.13.1 || >=16.0.0
Node Version
16.7.0
NPM Version
7.20.3
Score
99.5
Supply Chain
96.2
Quality
75.5
Maintenance
100
Vulnerability
100
License
Releases
4
Languages
2
JavaScript
TypeScript
JavaScript (80.48%)
TypeScript (19.52%)
Developer
sindresorhus
Download Statistics
Total Downloads
24,496,994,236
Last Day
29,569,095
Last Week
156,985,918
Last Month
633,942,044
Last Year
6,633,002,283
GitHub Statistics
MIT License
75 Stars
24 Commits
8 Forks
5 Watchers
1 Branches
6 Contributors
Updated on Apr 06, 2025
Bundle Size
1.60 kB
Minified
842.00 B
Minified + Gzipped
Sponsor this package
Maintainers
1
Package Meta Information
Latest Version
6.0.0
Package Id
p-locate@6.0.0
Size
3.00 kB
NPM Version
7.20.3
Node Version
16.7.0
Published on
Aug 25, 2021
Total Downloads
Cumulative downloads
Total Downloads
24,496,994,236
Last Day
4%
29,569,095
Compared to previous day
Last Week
13.1%
156,985,918
Compared to previous week
Last Month
1.7%
633,942,044
Compared to previous month
Last Year
15.8%
6,633,002,283
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
p-locate
Get the first fulfilled promise that satisfies the provided testing function
Think of it like an async version of Array#find.
Install
$ npm install p-locate
Usage
Here we find the first file that exists on disk, in array order.
1import {pathExists} from 'path-exists'; 2import pLocate from 'p-locate'; 3 4const files = [ 5 'unicorn.png', 6 'rainbow.png', // Only this one actually exists on disk 7 'pony.png' 8]; 9 10const foundPath = await pLocate(files, file => pathExists(file)); 11 12console.log(foundPath); 13//=> 'rainbow'
The above is just an example. Use locate-path if you need this.
API
pLocate(input, tester, options?)
Returns a Promise that is fulfilled when tester resolves to true or the iterable is done, or rejects if any of the promises reject. The fulfilled value is the current iterable value or undefined if tester never resolved to true.
input
Type: Iterable<Promise | unknown>
An iterable of promises/values to test.
tester(element)
Type: Function
This function will receive resolved values from input and is expected to return a Promise<boolean> or boolean.
options
Type: object
concurrency
Type: number
Default: Infinity
Minimum: 1
The number of concurrently pending promises returned by tester.
preserveOrder
Type: boolean
Default: true
Preserve input order when searching.
Disable this to improve performance if you don't care about the order.
Related
- p-map - Map over promises concurrently
- p-filter - Filter promises concurrently
- p-any - Wait for any promise to be fulfilled
- More…
Get professional support for this package with a Tidelift subscription
Tidelift helps make open source sustainable for maintainers while giving companies
assurances about security, maintenance, and licensing for their dependencies.
Tidelift helps make open source sustainable for maintainers while giving companies
assurances about security, maintenance, and licensing for their dependencies.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
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 binaries found in the repo
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 6/24 approved changesets -- score normalized to 2
Reason
2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
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
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/p-locate/main.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/p-locate/main.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/main.yml:22
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 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
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 6 are checked with a SAST tool
Score
4.4
/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.
Learn More