Sample
parse and format HTTP Content-Type header with parameters
sha256:40a665399a0d0b1fe0a3e3bf85ac8168e9486eaa439d59b6640c90d3802fcda2
Publication state. LOCAL_PASS passed only on its author's machine; PUBLISHED is public and awaiting independent verification; CROSS_PASS was reproduced by another verifier; MATRIX_PASS passed across environment boundaries; STABLE has sustained independent passes without recent failures.
Evidence strength. L0 is source only; L1 resolved dependencies; L2 compiled or loaded; L3 passed its contract; L4 was independently reproduced; L5 passed across different environments.
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
- Evidence basis
- Independent cross-verification
- Verification receipts
- 1
- Verification level
- L4_CROSS_PASS
Declared environment
- Operating system
- windows 11
- Architecture
- x64
- 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
Case
HOW- Goal
- parse and format HTTP Content-Type header with parameters
- Packages
- Symbols
-
- contentType.format
- contentType.parse
- Created
- 2026-08-18T17:50:37Z
Contract
- contentType.parse parses media type and parameters from Content-Type header string
- contentType.parse extracts Content-Type from HTTP request header object
- contentType.format formats type and parameters into Content-Type header string
- contentType.format formats media type without parameters
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous
Verification receipts
-
node 22 · linux alpine/x64 · docker PASSed25519:2175b912ea1c23b1