evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates how well the solution uses make-fetch-happen's streaming cache pipeline to tee HTTP responses into cacache while exposing integrity/size metadata, including support for late subscribers and cache reuse. Emphasis is on configuring the library's fetch options and response stream events rather than general code quality.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Cache path fetch",
"description": "Configures make-fetch-happen's fetch (or defaults chain) with a real `cachePath` so caching is handled by the dependency instead of manual file writes.",
"max_score": 25
},
{
"name": "Tee while streaming",
"description": "Streams `Response.body` once through the dependency-managed Minipass pipeline to the caller's destination while allowing the built-in cache writer to run concurrently (no duplicate reads or buffering hacks).",
"max_score": 20
},
{
"name": "Integrity option",
"description": "Supplies make-fetch-happen integrity verification (`integrity` plus optional `algorithms`/`size`) and handles EINTEGRITY or failed verification rather than skipping dependency-level checks.",
"max_score": 15
},
{
"name": "Late event delivery",
"description": "Hooks into the Minipass body events (`integrity`, `size`) and ensures handlers attached after data starts still receive the buffered payloads, leveraging CachingMinipassPipeline behavior instead of manual replays.",
"max_score": 20
},
{
"name": "Cache hit reuse",
"description": "On repeat requests, uses cache-aware modes (`force-cache`, `only-if-cached`, or equivalent `preferCache`) and inspects `x-local-cache*` headers/metadata to confirm cached responses are served without hitting the network.",
"max_score": 20
}
]
}