Sample
p-limit 7.3.1: Cap how many async tasks run at once with p-limit
Verified sample for npm p-limit 7.3.1: Cap how many async tasks run at once with p-limit. The contract ran on node 22 · linux alpine/x64 · docker and passed…
sha256:41fde54b3e3ec1ba86fcc07360372752a74c3a64e488689aa0a8c99ce1dc1c9c
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node 22 linux x64 node 22 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-13 |
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-17 |
Case
HOW- Goal
- Cap how many async tasks run at once with p-limit
- Packages
- Symbols
-
- pLimit
- Environment
- node 22
- Created
- 2026-08-13T15:20:35Z
Contract
- wrap each task with a limiter of concurrency 2
- assert no more than 2 tasks were ever in flight
- assert every task still ran and results keep input order
Files
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- test/contract.mjs