CodeSampleX

Sample

Prove that marked.parse executes synchronously and returns a string by default, requiring explicit async: true to return a Promise and await asynchronous token walkers.

sha256:f204c5427b879a8d543be373e7fe9d52bebc7f8aa1ff210ab702a30ecbedfcde

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
Prove that marked.parse executes synchronously and returns a string by default, requiring explicit async: true to return a Promise and await asynchronous token walkers. HOW
Packages
marked 18.0.5
Environment
node
Created
2026-08-17T22:03:38Z

Commonly assumed

marked.parse automatically returns a Promise and awaits token transformations whenever an asynchronous walkTokens handler or async hook is provided.

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