An offline, dated static scan for the model IDs and API surfaces that are scattered across source, configuration, environment defaults, and documentation — with days remaining and blast radius attached.
Public · synthetic demo · stdlib onlyA production app can still wake up broken on shutdown day because model references hide in settings, test fixtures, old modules, and runtime routers. This radar builds the inventory. It does not perform the migration.
| reference | deadline state | evidence path |
|---|---|---|
gemini-2.0-flash | RETIRED · −62 days | legacy_google.py:1 |
temperature on Opus 4.8 | RETIRED · immediate | anthropic_client.py:1 |
claude-opus-4-1-20250805 | CRITICAL · 3 days | config.yaml:2 |
| Assistants API | CRITICAL · 24 days | app.py:4 |
gpt-4-0613 | WARN · 82 days | app.py:3 |
The Gemini reference is already past its published shutdown date. If that path still executes and depends on the retired model, it is already broken; static analysis alone cannot prove that the file is live or reachable.
dynamic f-string → Unverified hypotheses runtime MODELS router → Unverified hypotheses remote config service → Additional data required
Dynamic selection is never promoted to Confirmed and never presented as clean. Runtime logs are the missing evidence.
The twelfth planted case is the current-model negative control and correctly produces no finding. Provider snapshots are dated and the weekly CI run fails when a live-code finding is retired or inside the configured deadline.
Confirmed evidence exact literal registry match Likely strong indirect reference, such as an env default Unverified hypotheses dynamic construction or runtime router Additional data required remote config, database, or feature-flag evidence
· Static analysis cannot resolve model names chosen at runtime. · This tool inventories references and deadlines; it does not perform migrations. · Vendor dates come from dated registry snapshots and must be re-verified at source. · A clean report means “nothing matched the registry,” not “your system is safe.” · A static reference does not prove that a file is deployed, reachable, or executed.