{
  "repo": "kong",
  "full_name": "tidbcloud/kong",
  "status": "scan_complete",
  "scan_started_at": "2026-04-01T23:03:15+08:00",
  "scan_completed_at": "2026-04-01T23:03:15+08:00",
  "expected_binaries": [
    {
      "name": "kong",
      "path": "bin/kong",
      "status": "completed",
      "role": "primary_service"
    }
  ],
  "scanned_binaries": [
    {
      "name": "kong",
      "path": "bin/kong",
      "type": "lua_service_cli",
      "status": "completed",
      "interfaces_file": "interfaces/bin-kong.json",
      "service_mapping_file": "service-mapping/bin-kong.json",
      "external_services": 3
    }
  ],
  "skipped_binaries": [],
  "files_generated": [
    "interfaces/bin-kong.json",
    "service-mapping/bin-kong.json"
  ],
  "scan_progress": {
    "completed": 1,
    "skipped": 0,
    "total": 1
  },
  "review_status": "pending_review",
  "codex_scan_at": "2026-04-01T23:03:15+08:00",
  "codex_scan_verdict": "scan_complete",
  "codex_scan_note": "Manual metadata validation confirmed kong is not a deployment-config repository. The repo contains the Kong API Gateway runtime, started via bin/kong and kong.cmd.init, with documented proxy traffic listeners on :8000 and an Admin API on :8001 plus CLI-driven lifecycle and migration flows."
}