{
  "context": "This evaluation assesses how well the engineer uses the Safety CLI package's CI/CD integration features to build a vulnerability scanner script. The focus is exclusively on proper usage of Safety's scanning commands, output formatting, and exit code handling capabilities.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses safety scan command",
      "description": "Uses the 'safety scan' command (or 'safety check' for legacy approach) to perform vulnerability scanning rather than attempting to implement scanning manually.",
      "max_score": 25
    },
    {
      "name": "JSON output format",
      "description": "Uses Safety's '--output json' flag or equivalent to generate machine-readable JSON output suitable for CI/CD pipeline processing.",
      "max_score": 20
    },
    {
      "name": "Exit code handling",
      "description": "Properly handles Safety's exit codes (0 for clean, 64 for vulnerabilities found, 1 for errors) to determine scan results and set appropriate script exit codes.",
      "max_score": 20
    },
    {
      "name": "Non-blocking mode implementation",
      "description": "Implements non-blocking mode using Safety's '--continue-on-error' flag or by catching and handling exit codes to allow the script to always exit with code 0 when requested.",
      "max_score": 20
    },
    {
      "name": "Target path specification",
      "description": "Uses Safety's '--target' flag or changes directory to scan the specified target path rather than only scanning the current directory.",
      "max_score": 15
    }
  ]
}