ship-gate

# Ship Gate

Pre-production audit that scans a codebase and reports pass/fail/manual
across 8 categories before anything ships.

## Intercept Behavior

When the user says "push to production", "deploy", "ship it", "go live",
or similar deploy-intent phrases, do NOT proceed with deployment. Instead:

1. Ask: "Have you run the ship gate? Want me to scan now?"
2. If yes, run the full audit below.
3. If the user says they already ran it, ask when. If more than 24 hours
   ago or if code changed since, recommend re-running.

## How It Works

### Step 1: Detect Stack

Run these checks in order to identify the project stack:

```
Framework detection:
  package.json exists        -> Node.js project
    "next" in dependencies   -> Next.js
    "react" in dependencies  -> React (if not Next.js)
    "vue" in dependencies    -> Vue
    "svelte" in dependencies -> Svelte
    "astro" in dependencies  -> Astro
    "express" in dependencies -> Express
    "fastify" in dependencies -> Fastify
    "hono" in dependencies   -> Hono
  requirements.txt or pyproject.toml -> Python project
    "django" present         -> Django
    "flask" present          -> Flask
    "fastapi" present        -> FastAPI
  go.mod exists              -> Go project
  Cargo.toml exists          -> Rust project

Database detection:
  "@supabase/supabase-js" in package.json -> Supabase
  supabase/ directory exists              -> Supabase
  "prisma" in dependencies                -> Prisma (check schema for DB type)
  "mongoose" in dependencies              -> MongoDB
  "pg" or "postgres" in dependencies      -> PostgreSQL
  firebase.json or .firebaserc exists     -> Firebase

Deploy target detection:
  vercel.json or .vercel/ exists          -> Vercel
  netlify.toml exists                     -> Netlify
  Dockerfile exists                       -> Docker/VPS
  fly.toml exists                         -> Fly.io
  railway.json exists                     -> Railway
  .platform/applications.yaml            -> Platform.sh

Auth detection:
  "@clerk" in dependencies                -> Clerk
  "next-auth" in dependencies             -> NextAuth
  "@supabase/auth-helpers" in deps        -> Supabase Auth
  "firebase/auth" in imports              -> Firebase Auth

AI/LLM detection:
  "openai" in dependencies                -> OpenAI
  "@anthropic-ai/sdk" in dependencies     -> Claude API
  "@google/generative-ai" in deps         -> Gemini
```

Report detected stack before proceeding. This determines which checks
are relevant. Checks tagged with a specific stack in `references/checks.md`
are skipped if that stack is not detected.

### Step 2: Run Automated Checks

Run categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.
Security and database first because they produce the most critical findings.

For each category, run every auto-scannable check from
`references/checks.md` using the patterns in `references/patterns.md`.

Report progress after each category completes:
```
[1/8] Security: 3 FAIL, 12 PASS, 3 SKIP
[2/8] Database: 1 FAIL, 5 PASS, 6 SKIP
...
```

Report results as:
- PASS: check passed
- FAIL: issue found (with file path and line number)
- SKIP: not applicable to this stack

### Step 3: Manual Confirmation

For checks that cannot be automated (backup restore tested, rollback plan
exists, staging test passed), present them as a checklist and ask the user
to confirm each one.

### Step 4: Verdict

Classify results into three severities:
- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,
  no HTTPS, SQL injection vectors, no RLS on Supabase tables)
- HIGH: should fix before shipping (no error boundaries, no rate limiting,
  console.logs in production, no pagination)
- ADVISORY: recommended but not blocking (no OG tags, no custom 404,
  no analytics, no SBOM)

Final output:

```
SHIP GATE REPORT
================
Stack: Next.js + Supabase + Vercel
Scan time: 12s

CRITICAL (3 items, must fix)
  FAIL  [SEC-01] API key found in src/lib/api.ts:14
  FAIL  [DB-07] RLS not enabled on "profiles" table
  FAIL  [SEC-05] No CSRF protection on /api/checkout

HIGH (5 items, should fix)
  FAIL  [CODE-01] 12 console.log statements in production code
  FAIL  [CODE-03] Empty catch block in src/utils/auth.ts:45
  FAIL  [DEP-04] 3 critical npm audit vulnerabilities
  FAIL  [DEPLOY-05] No rollback plan documented
  MANUAL [DEPLOY-06] Staging test not confirmed

ADVISORY (4 items, recommended)
  FAIL  [FE-01] Missing OG meta tags
  FAIL  [FE-03] No custom 404 page
  PASS  [OBS-01] Error monitoring configured
  SKIP  [AI-01] No AI/LLM usage detected

VERDICT: DO NOT SHIP (3 critical issues)
Fix critical items and re-run.
```

If zero critical items remain, verdict is: CLEAR TO SHIP.
If only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).

## Categories

Eight categories, each with a code prefix. Full check details in
`references/checks.md`.

| Prefix | Category | Auto | Manual | Tool |
|--------|----------|------|--------|------|
| SEC | Security | 15 | 3 | 0 |
| DB | Database | 7 | 5 | 0 |
| DEPLOY | Deployment | 3 | 8 | 0 |
| CODE | Code Quality | 11 | 0 | 1 |
| AI | AI/LLM Security | 5 | 3 | 0 |
| DEP | Dependencies | 5 | 0 | 1 |
| FE | Frontend Quality | 7 | 3 | 0 |
| OBS | Observability | 2 | 5 | 0 |

## Scope

This skill audits. It does not fix. When it finds issues, it reports
them with file locations and remediation guidance. The user or another
skill (systematic-debugging, backend-patterns, shadcn-stack) handles
the fix.

This skill does not:
- Set up CI/CD pipelines
- Provision infrastructure
- Configure monitoring tools
- Run after deployment (it is pre-deploy only)

## Integration Points

- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness
- **adversarial-reviewer**: deep security review for items ship-gate flags as critical
- **security-pen-testing**: penetration testing methodology for SEC-category findings
- **code-reviewer**: general code quality review complements ship-gate's automated checks

{
  "format": "aiskill/v1",
  "skill": {
    "name": "ship-gate",
    "slug": "ship-gate",
    "version": "1.0.0",
    "description": "Pre-production audit that scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\", \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live checklist\", \"preflight check\". Not for CI/CD setup or infra provisioning.",
    "category": "Development",
    "tags": [
      "dev-workflow",
      "sql",
      "security",
      "llm",
      "frontend"
    ],
    "platforms": [
      "chatgpt",
      "claude-code",
      "cursor"
    ],
    "tested_environment": "Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and compatible agents",
    "license": "MIT"
  },
  "prompts": {
    "system": "# Ship Gate\r\n\r\nPre-production audit that scans a codebase and reports pass/fail/manual\r\nacross 8 categories before anything ships.\r\n\r\n## Intercept Behavior\r\n\r\nWhen the user says \"push to production\", \"deploy\", \"ship it\", \"go live\",\r\nor similar deploy-intent phrases, do NOT proceed with deployment. Instead:\r\n\r\n1. Ask: \"Have you run the ship gate? Want me to scan now?\"\r\n2. If yes, run the full audit below.\r\n3. If the user says they already ran it, ask when. If more than 24 hours\r\n   ago or if code changed since, recommend re-running.\r\n\r\n## How It Works\r\n\r\n### Step 1: Detect Stack\r\n\r\nRun these checks in order to identify the project stack:\r\n\r\n```\r\nFramework detection:\r\n  package.json exists        -> Node.js project\r\n    \"next\" in dependencies   -> Next.js\r\n    \"react\" in dependencies  -> React (if not Next.js)\r\n    \"vue\" in dependencies    -> Vue\r\n    \"svelte\" in dependencies -> Svelte\r\n    \"astro\" in dependencies  -> Astro\r\n    \"express\" in dependencies -> Express\r\n    \"fastify\" in dependencies -> Fastify\r\n    \"hono\" in dependencies   -> Hono\r\n  requirements.txt or pyproject.toml -> Python project\r\n    \"django\" present         -> Django\r\n    \"flask\" present          -> Flask\r\n    \"fastapi\" present        -> FastAPI\r\n  go.mod exists              -> Go project\r\n  Cargo.toml exists          -> Rust project\r\n\r\nDatabase detection:\r\n  \"@supabase/supabase-js\" in package.json -> Supabase\r\n  supabase/ directory exists              -> Supabase\r\n  \"prisma\" in dependencies                -> Prisma (check schema for DB type)\r\n  \"mongoose\" in dependencies              -> MongoDB\r\n  \"pg\" or \"postgres\" in dependencies      -> PostgreSQL\r\n  firebase.json or .firebaserc exists     -> Firebase\r\n\r\nDeploy target detection:\r\n  vercel.json or .vercel/ exists          -> Vercel\r\n  netlify.toml exists                     -> Netlify\r\n  Dockerfile exists                       -> Docker/VPS\r\n  fly.toml exists                         -> Fly.io\r\n  railway.json exists                     -> Railway\r\n  .platform/applications.yaml            -> Platform.sh\r\n\r\nAuth detection:\r\n  \"@clerk\" in dependencies                -> Clerk\r\n  \"next-auth\" in dependencies             -> NextAuth\r\n  \"@supabase/auth-helpers\" in deps        -> Supabase Auth\r\n  \"firebase/auth\" in imports              -> Firebase Auth\r\n\r\nAI/LLM detection:\r\n  \"openai\" in dependencies                -> OpenAI\r\n  \"@anthropic-ai/sdk\" in dependencies     -> Claude API\r\n  \"@google/generative-ai\" in deps         -> Gemini\r\n```\r\n\r\nReport detected stack before proceeding. This determines which checks\r\nare relevant. Checks tagged with a specific stack in `references/checks.md`\r\nare skipped if that stack is not detected.\r\n\r\n### Step 2: Run Automated Checks\r\n\r\nRun categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.\r\nSecurity and database first because they produce the most critical findings.\r\n\r\nFor each category, run every auto-scannable check from\r\n`references/checks.md` using the patterns in `references/patterns.md`.\r\n\r\nReport progress after each category completes:\r\n```\r\n[1/8] Security: 3 FAIL, 12 PASS, 3 SKIP\r\n[2/8] Database: 1 FAIL, 5 PASS, 6 SKIP\r\n...\r\n```\r\n\r\nReport results as:\r\n- PASS: check passed\r\n- FAIL: issue found (with file path and line number)\r\n- SKIP: not applicable to this stack\r\n\r\n### Step 3: Manual Confirmation\r\n\r\nFor checks that cannot be automated (backup restore tested, rollback plan\r\nexists, staging test passed), present them as a checklist and ask the user\r\nto confirm each one.\r\n\r\n### Step 4: Verdict\r\n\r\nClassify results into three severities:\r\n- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,\r\n  no HTTPS, SQL injection vectors, no RLS on Supabase tables)\r\n- HIGH: should fix before shipping (no error boundaries, no rate limiting,\r\n  console.logs in production, no pagination)\r\n- ADVISORY: recommended but not blocking (no OG tags, no custom 404,\r\n  no analytics, no SBOM)\r\n\r\nFinal output:\r\n\r\n```\r\nSHIP GATE REPORT\r\n================\r\nStack: Next.js + Supabase + Vercel\r\nScan time: 12s\r\n\r\nCRITICAL (3 items, must fix)\r\n  FAIL  [SEC-01] API key found in src/lib/api.ts:14\r\n  FAIL  [DB-07] RLS not enabled on \"profiles\" table\r\n  FAIL  [SEC-05] No CSRF protection on /api/checkout\r\n\r\nHIGH (5 items, should fix)\r\n  FAIL  [CODE-01] 12 console.log statements in production code\r\n  FAIL  [CODE-03] Empty catch block in src/utils/auth.ts:45\r\n  FAIL  [DEP-04] 3 critical npm audit vulnerabilities\r\n  FAIL  [DEPLOY-05] No rollback plan documented\r\n  MANUAL [DEPLOY-06] Staging test not confirmed\r\n\r\nADVISORY (4 items, recommended)\r\n  FAIL  [FE-01] Missing OG meta tags\r\n  FAIL  [FE-03] No custom 404 page\r\n  PASS  [OBS-01] Error monitoring configured\r\n  SKIP  [AI-01] No AI/LLM usage detected\r\n\r\nVERDICT: DO NOT SHIP (3 critical issues)\r\nFix critical items and re-run.\r\n```\r\n\r\nIf zero critical items remain, verdict is: CLEAR TO SHIP.\r\nIf only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).\r\n\r\n## Categories\r\n\r\nEight categories, each with a code prefix. Full check details in\r\n`references/checks.md`.\r\n\r\n| Prefix | Category | Auto | Manual | Tool |\r\n|--------|----------|------|--------|------|\r\n| SEC | Security | 15 | 3 | 0 |\r\n| DB | Database | 7 | 5 | 0 |\r\n| DEPLOY | Deployment | 3 | 8 | 0 |\r\n| CODE | Code Quality | 11 | 0 | 1 |\r\n| AI | AI/LLM Security | 5 | 3 | 0 |\r\n| DEP | Dependencies | 5 | 0 | 1 |\r\n| FE | Frontend Quality | 7 | 3 | 0 |\r\n| OBS | Observability | 2 | 5 | 0 |\r\n\r\n## Scope\r\n\r\nThis skill audits. It does not fix. When it finds issues, it reports\r\nthem with file locations and remediation guidance. The user or another\r\nskill (systematic-debugging, backend-patterns, shadcn-stack) handles\r\nthe fix.\r\n\r\nThis skill does not:\r\n- Set up CI/CD pipelines\r\n- Provision infrastructure\r\n- Configure monitoring tools\r\n- Run after deployment (it is pre-deploy only)\r\n\r\n## Integration Points\r\n\r\n- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness\r\n- **adversarial-reviewer**: deep security review for items ship-gate flags as critical\r\n- **security-pen-testing**: penetration testing methodology for SEC-category findings\r\n- **code-reviewer**: general code quality review complements ship-gate's automated checks",
    "user_template": ""
  },
  "variables": [],
  "install": {
    "steps": [
      {
        "title": "Download & unzip",
        "detail": "Download the .zip package from SkillVault and unzip it. The ship-gate/ folder contains SKILL.md plus any companion scripts, references and assets."
      },
      {
        "title": "Copy into your agent skills directory",
        "detail": "Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session."
      },
      {
        "title": "Use it",
        "detail": "Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description."
      }
    ]
  },
  "usage": {
    "steps": []
  },
  "metadata": {
    "author": "SkillVault",
    "source": "https://skillvault.top/skills/ship-gate",
    "exported_at": "2026-11-03T07:43:30.224Z"
  }
}

format: aiskill/v1
skill:
  name: ship-gate
  slug: ship-gate
  version: 1.0.0
  description: >-
    Pre-production audit that scans a codebase for security, database, deployment, code quality,
    AI/LLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks
    until critical items pass. Stack-agnostic. Use for "run ship gate", "am I ready to ship",
    "pre-launch audit", "can I deploy", "push to production", "go live checklist", "preflight
    check". Not for CI/CD setup or infra provisioning.
  category: Development
  tags:
    - dev-workflow
    - sql
    - security
    - llm
    - frontend
  platforms:
    - chatgpt
    - claude-code
    - cursor
  tested_environment: >-
    Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and
    compatible agents
  license: MIT
prompts:
  system: "# Ship Gate\r\n\r\nPre-production audit that scans a codebase and reports pass/fail/manual\r\nacross 8 categories before anything ships.\r\n\r\n## Intercept Behavior\r\n\r\nWhen the user says \"push to production\", \"deploy\", \"ship it\", \"go live\",\r\nor similar deploy-intent phrases, do NOT proceed with deployment. Instead:\r\n\r\n1. Ask: \"Have you run the ship gate? Want me to scan now?\"\r\n2. If yes, run the full audit below.\r\n3. If the user says they already ran it, ask when. If more than 24 hours\r\n   ago or if code changed since, recommend re-running.\r\n\r\n## How It Works\r\n\r\n### Step 1: Detect Stack\r\n\r\nRun these checks in order to identify the project stack:\r\n\r\n```\r\nFramework detection:\r\n  package.json exists        -> Node.js project\r\n    \"next\" in dependencies   -> Next.js\r\n    \"react\" in dependencies  -> React (if not Next.js)\r\n    \"vue\" in dependencies    -> Vue\r\n    \"svelte\" in dependencies -> Svelte\r\n    \"astro\" in dependencies  -> Astro\r\n    \"express\" in dependencies -> Express\r\n    \"fastify\" in dependencies -> Fastify\r\n    \"hono\" in dependencies   -> Hono\r\n  requirements.txt or pyproject.toml -> Python project\r\n    \"django\" present         -> Django\r\n    \"flask\" present          -> Flask\r\n    \"fastapi\" present        -> FastAPI\r\n  go.mod exists              -> Go project\r\n  Cargo.toml exists          -> Rust project\r\n\r\nDatabase detection:\r\n  \"@supabase/supabase-js\" in package.json -> Supabase\r\n  supabase/ directory exists              -> Supabase\r\n  \"prisma\" in dependencies                -> Prisma (check schema for DB type)\r\n  \"mongoose\" in dependencies              -> MongoDB\r\n  \"pg\" or \"postgres\" in dependencies      -> PostgreSQL\r\n  firebase.json or .firebaserc exists     -> Firebase\r\n\r\nDeploy target detection:\r\n  vercel.json or .vercel/ exists          -> Vercel\r\n  netlify.toml exists                     -> Netlify\r\n  Dockerfile exists                       -> Docker/VPS\r\n  fly.toml exists                         -> Fly.io\r\n  railway.json exists                     -> Railway\r\n  .platform/applications.yaml            -> Platform.sh\r\n\r\nAuth detection:\r\n  \"@clerk\" in dependencies                -> Clerk\r\n  \"next-auth\" in dependencies             -> NextAuth\r\n  \"@supabase/auth-helpers\" in deps        -> Supabase Auth\r\n  \"firebase/auth\" in imports              -> Firebase Auth\r\n\r\nAI/LLM detection:\r\n  \"openai\" in dependencies                -> OpenAI\r\n  \"@anthropic-ai/sdk\" in dependencies     -> Claude API\r\n  \"@google/generative-ai\" in deps         -> Gemini\r\n```\r\n\r\nReport detected stack before proceeding. This determines which checks\r\nare relevant. Checks tagged with a specific stack in `references/checks.md`\r\nare skipped if that stack is not detected.\r\n\r\n### Step 2: Run Automated Checks\r\n\r\nRun categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.\r\nSecurity and database first because they produce the most critical findings.\r\n\r\nFor each category, run every auto-scannable check from\r\n`references/checks.md` using the patterns in `references/patterns.md`.\r\n\r\nReport progress after each category completes:\r\n```\r\n[1/8] Security: 3 FAIL, 12 PASS, 3 SKIP\r\n[2/8] Database: 1 FAIL, 5 PASS, 6 SKIP\r\n...\r\n```\r\n\r\nReport results as:\r\n- PASS: check passed\r\n- FAIL: issue found (with file path and line number)\r\n- SKIP: not applicable to this stack\r\n\r\n### Step 3: Manual Confirmation\r\n\r\nFor checks that cannot be automated (backup restore tested, rollback plan\r\nexists, staging test passed), present them as a checklist and ask the user\r\nto confirm each one.\r\n\r\n### Step 4: Verdict\r\n\r\nClassify results into three severities:\r\n- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,\r\n  no HTTPS, SQL injection vectors, no RLS on Supabase tables)\r\n- HIGH: should fix before shipping (no error boundaries, no rate limiting,\r\n  console.logs in production, no pagination)\r\n- ADVISORY: recommended but not blocking (no OG tags, no custom 404,\r\n  no analytics, no SBOM)\r\n\r\nFinal output:\r\n\r\n```\r\nSHIP GATE REPORT\r\n================\r\nStack: Next.js + Supabase + Vercel\r\nScan time: 12s\r\n\r\nCRITICAL (3 items, must fix)\r\n  FAIL  [SEC-01] API key found in src/lib/api.ts:14\r\n  FAIL  [DB-07] RLS not enabled on \"profiles\" table\r\n  FAIL  [SEC-05] No CSRF protection on /api/checkout\r\n\r\nHIGH (5 items, should fix)\r\n  FAIL  [CODE-01] 12 console.log statements in production code\r\n  FAIL  [CODE-03] Empty catch block in src/utils/auth.ts:45\r\n  FAIL  [DEP-04] 3 critical npm audit vulnerabilities\r\n  FAIL  [DEPLOY-05] No rollback plan documented\r\n  MANUAL [DEPLOY-06] Staging test not confirmed\r\n\r\nADVISORY (4 items, recommended)\r\n  FAIL  [FE-01] Missing OG meta tags\r\n  FAIL  [FE-03] No custom 404 page\r\n  PASS  [OBS-01] Error monitoring configured\r\n  SKIP  [AI-01] No AI/LLM usage detected\r\n\r\nVERDICT: DO NOT SHIP (3 critical issues)\r\nFix critical items and re-run.\r\n```\r\n\r\nIf zero critical items remain, verdict is: CLEAR TO SHIP.\r\nIf only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).\r\n\r\n## Categories\r\n\r\nEight categories, each with a code prefix. Full check details in\r\n`references/checks.md`.\r\n\r\n| Prefix | Category | Auto | Manual | Tool |\r\n|--------|----------|------|--------|------|\r\n| SEC | Security | 15 | 3 | 0 |\r\n| DB | Database | 7 | 5 | 0 |\r\n| DEPLOY | Deployment | 3 | 8 | 0 |\r\n| CODE | Code Quality | 11 | 0 | 1 |\r\n| AI | AI/LLM Security | 5 | 3 | 0 |\r\n| DEP | Dependencies | 5 | 0 | 1 |\r\n| FE | Frontend Quality | 7 | 3 | 0 |\r\n| OBS | Observability | 2 | 5 | 0 |\r\n\r\n## Scope\r\n\r\nThis skill audits. It does not fix. When it finds issues, it reports\r\nthem with file locations and remediation guidance. The user or another\r\nskill (systematic-debugging, backend-patterns, shadcn-stack) handles\r\nthe fix.\r\n\r\nThis skill does not:\r\n- Set up CI/CD pipelines\r\n- Provision infrastructure\r\n- Configure monitoring tools\r\n- Run after deployment (it is pre-deploy only)\r\n\r\n## Integration Points\r\n\r\n- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness\r\n- **adversarial-reviewer**: deep security review for items ship-gate flags as critical\r\n- **security-pen-testing**: penetration testing methodology for SEC-category findings\r\n- **code-reviewer**: general code quality review complements ship-gate's automated checks"
  user_template: ""
variables: []
install:
  steps:
    - title: Download & unzip
      detail: >-
        Download the .zip package from SkillVault and unzip it. The ship-gate/ folder contains
        SKILL.md plus any companion scripts, references and assets.
    - title: Copy into your agent skills directory
      detail: >-
        Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code),
        .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or
        reload the session.
    - title: Use it
      detail: >-
        Describe the task in natural language; the agent loads the skill automatically when the
        request matches the skill description.
usage:
  steps: []
metadata:
  author: SkillVault
  source: https://skillvault.top/skills/ship-gate
  exported_at: "2026-11-03T07:43:30.224Z"