llm-deprecation-radar - shutdown-date scan

An offline, dated static scan for the model IDs and API surfaces scattered across source, configuration, environment defaults and documentation - with days remaining and blast radius attached.

The problem. The vendor publishes a date. The codebase forgets where the dependency lives. A production app can wake up broken on shutdown day because model references hide in settings, test fixtures, old modules and runtime routers.

This builds the inventory. It does not perform the migration, and it does not pretend to.

Evidence stays in its lane: 6 confirmed references, 2 likely, 2 unverified hypotheses, 1 needing runtime data. Static analysis cannot resolve dynamically constructed model names, so the report says so rather than guessing.

Every registry entry carries a vendor source URL and a snapshot date, so each deadline is auditable rather than asserted. Standard library only, no network calls at scan time.

Code: github.com/jigonyoo/llm-deprecation-radar