Catch deprecated model IDs before your build does

A tiny CLI and GitHub Action that scans your codebase for pinned AI model IDs and warns when they're on the deprecation departure board — using the live Platform Ledger. Put our deprecation calendar in your CI.

$ npx wreck-watch

wreck-watch: scanning for pinned model IDs…

  ⚠  gpt-4o-2024-05-13        3 files   shutdown 2026-10-23 (99 days)   replacement: gpt-5.5
  ⚠  claude-opus-4-1-20250805 1 file    shutdown 2026-08-05 (20 days)   replacement: claude-opus-4-8
  ✓  gemini-embedding-2       2 files   no scheduled shutdown

2 models on the departure board. Deprecation data: projectwrecked.com/platform-ledger
Write the clause: projectwrecked.com/articles/the-model-deprecation-clause

Never breaks your build

Exits 0 by default. Only --strict can fail a job, and only for a model inside your window.

No telemetry

Exactly one network call — the public deprecation JSON. Nothing about you or your code leaves the machine.

Fails soft

Site down? It uses a bundled snapshot, skips the freshness check, and exits 0. CI never breaks because a website hiccuped.

Use it

Zero install, zero config. Scans source, config and .env.example, honours .gitignore.

npx wreck-watch                  # scan, always exits 0
npx wreck-watch --strict         # exit 1 if a pinned model is within 90 days of shutdown
npx wreck-watch --strict --days 30

In GitHub Actions

Two lines. It annotates the run with any warnings:

# .github/workflows/wreck-watch.yml
name: wreck-watch
on: [pull_request]
jobs:
  wreck-watch:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: leegoodenough/wreck-watch@v1
        with:
          days: '60'

📅

Every warning puts a real shutdown date and a replacement in your build log, at the moment you can still do something about it. Source on GitHub; deprecation data from the Platform Ledger. Then write the clause so the migration is scoped, not sprung.