CodeSampleX

Sample

Prove fast-glob 3.3.3 fg.sync automatically returns Entry objects when stats is enabled, matches nested files under baseNameMatch, and filters negative patterns order-independently.

sha256:5251911711e9f7f3cb619b6716cac28a82f6483b9b547ce8e0293ee3827a3a73

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-18

Case

Goal
Prove fast-glob 3.3.3 fg.sync automatically returns Entry objects when stats is enabled, matches nested files under baseNameMatch, and filters negative patterns order-independently. HOW
Packages
fast-glob 3.3.3
Environment
node
Created
2026-08-18T01:23:46Z

Commonly assumed

fg.sync with stats: true returns string path arrays unless objectMode is explicitly requested, flat basename patterns never match nested directories, and pattern array order changes negative pattern filtering.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts