{
  "context": "This criteria evaluates how well an engineer uses Node.js file system APIs to detect package managers by scanning for lockfiles in the directory hierarchy. It focuses on the proper usage of fs module functions for directory traversal and file existence checking.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "File existence checking",
      "description": "Uses fs.existsSync() or fs.accessSync() to check for the presence of lockfiles (pnpm-lock.yaml, yarn.lock, package-lock.json, bun.lockb, bun.lock, deno.lock) in directories",
      "max_score": 25
    },
    {
      "name": "Path resolution",
      "description": "Uses path.resolve() or path.join() to construct proper file paths when combining directory paths with lockfile names",
      "max_score": 15
    },
    {
      "name": "Directory traversal",
      "description": "Uses path.dirname() to traverse up the directory hierarchy from the starting path to parent directories until reaching the filesystem root",
      "max_score": 25
    },
    {
      "name": "Root detection",
      "description": "Uses path.parse() or comparison logic to detect when the filesystem root has been reached and stop traversal",
      "max_score": 15
    },
    {
      "name": "Priority-based detection",
      "description": "Implements the lockfile detection in priority order (pnpm first, then yarn, npm, bun, deno) by checking files sequentially at each directory level",
      "max_score": 15
    },
    {
      "name": "Default fallback",
      "description": "Returns 'npm' as the default package manager when no lockfile is found after complete directory traversal",
      "max_score": 5
    }
  ]
}