{
  "context": "Evaluates whether the solution configures npm via its CLI to set registries, persist tokens, and confirm authenticated identity as required by the spec.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Default registry",
      "description": "Uses `npm config set registry <url>` and, when requested, `npm config set always-auth true` to apply the default registry through npm (including `--userconfig <path>` when a custom config file is provided).",
      "max_score": 25
    },
    {
      "name": "Scoped registry",
      "description": "Maps a provided scope to its registry with `npm config set @<scope>:registry <url>` while leaving the default registry untouched, honoring any custom config path via npm's CLI flags.",
      "max_score": 25
    },
    {
      "name": "Auth token store",
      "description": "Persists the supplied token using npm's expected key (e.g., `npm config set //<registry-host>/:_authToken <token>`) rather than manual file edits, using the correct registry host and optional user config path.",
      "max_score": 25
    },
    {
      "name": "Identity check",
      "description": "Runs an npm command such as `npm whoami` (or `npm profile get --json`) against the configured registry to return the authenticated username when verification is requested, reusing the written config for auth context.",
      "max_score": 25
    }
  ]
}