evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates whether the solution leverages cacache's listing and entry-inspection APIs to build cache inventory helpers. Focuses on using ls/ls.stream for full listings, get.info for single lookups, and deriving summaries directly from package data without manual filesystem work.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Cache listing",
"description": "Uses cacache.ls or cacache.ls.stream to enumerate entries for the provided cache path instead of manual filesystem traversal, and produces a key-ascending list.",
"max_score": 35
},
{
"name": "Entry metadata",
"description": "Returns integrity, size, metadata, and time fields sourced from cacache listing data without recomputing or omitting them.",
"max_score": 20
},
{
"name": "Single lookup",
"description": "Uses cacache.get.info to retrieve a specific key's entry (without fetching content) and propagates not-found errors as rejections rather than substituting fallback values.",
"max_score": 30
},
{
"name": "Summary via listing",
"description": "Computes entry count and total size from the cacache listing results (ls/ls.stream) without redundant reads of cache content or filesystem stats.",
"max_score": 15
}
]
}