Sample
Show that picomatch's extglob negation does not match like Bash greedily.
sha256:b8544e8b7e053ceac9aaa4fb328c5d5268fded6d853cc97e082db7f576963962
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- node
- Operating system
- linux
- Architecture
- x64
- Runtime
- node
- Language
- node
- Package manager
- npm
Verification-run environments
- Execution context
- node 22
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- node 22
- Language
- javascript
- Package manager
- npm
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17
Case
- Goal
- Show that picomatch's extglob negation does not match like Bash greedily. HOW
- Packages
-
picomatch 4.0.5
- Environment
- node
- Created
- 2026-08-17T03:51:49Z
Commonly assumed
A competent caller expects `!(foo)*` to match `foo` and `foobar` the way a Bash-style extglob does.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert picomatch.isMatch('foo', '!(foo)*') is false
- assert picomatch.isMatch('foobar', '!(foo)*') is false
- assert picomatch.isMatch('bar', '!(foo)*') is true
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9