🌅 llm-sunset
Your app is about to break because an AI provider is shutting down the model it uses. llm-sunset tells you before it happens.
OpenAI, Anthropic, Google, Groq, Cohere and xAI retire models constantly, often with only a few months' notice. The model ID sits hard-coded in some config file and nobody notices until production starts returning 404 model_not_found.
llm-sunset scans your code, finds every AI model ID, and checks it against a daily-updated list of official deprecation notices.
$ llm-sunset
app/llm.py:12:23 error OpenAI model 'gpt-4o-2024-05-13' retires 2026-10-23 (16 days left); replace with: gpt-5.6-sol
app/summarize.py:8:11 error OpenAI model 'gpt-3.5-turbo' retires 2026-10-23 (16 days left); replace with: gpt-5.6-terra
config/models.yaml:3:8 error Anthropic model 'claude-2.0' RETIRED on 2025-07-21 (443 days ago); replace with: claude-opus-4-8
worker/.env:2:7 warning Anthropic model 'claude-sonnet-4-5-20250929' retires 2026-11-30 (54 days left)
4 finding(s): 3 error(s), 1 warning(s)
- Zero dependencies. Pure Python standard library, Python 3.8+.
- Works offline. Ships with a bundled snapshot; uses live data when it can reach it.
- No API keys, and your code never leaves your machine. It only downloads a public JSON file.
- CI-ready. Comes with a GitHub Action, a pre-commit hook, SARIF output for GitHub code scanning, JSON and Markdown.
- Low noise. It matches exact model IDs (so
gpt-4o-miniis not reported asgpt-4o, andgpt-4.1is not reported asgpt-4). Generic one-word IDs (command,ada,whisper,davinci…) only count next to model context — amodel:/engine=key, a provider or SDK name, or aprovider/prefix — so everyday words like the"command"key in MCP configs don't trigger it. Dot-directories (.zcode/,.qwen/…), logs (*.log,*.jsonl), lockfiles andnode_modulesare skipped, and.gitignoreis respected.
Install
pipx install llm-sunset # or: pip install llm-sunset / uvx llm-sunset
Usage
llm-sunset # scan current directory
llm-sunset src/ config/ # scan specific paths
llm-sunset --provider openai # only OpenAI notices (repeatable)
llm-sunset --fail-within 30 # only fail on models retiring within 30 days
llm-sunset --format json # also: markdown, sarif, github
llm-sunset info gpt-4o-2024-05-13 # look up a model
llm-sunset upcoming --days 90 # every shutdown in the next 90 days
Exit code is 1 if any model is already retired or retires within --fail-within days (default 90). Use --no-fail to only report.
Ignoring things: put llm-sunset: ignore in a comment on a line, or llm-sunset: ignore-file anywhere in a file. Use --exclude 'tests/*' for paths. Markdown/RST/TXT files are skipped unless you pass --include-docs. Files ignored by .gitignore are skipped unless you pass --no-gitignore.
Azure, Vertex AI and Bedrock publish their own retirement dates for models they resell, which often differ from the original provider's dates. To avoid false alarms these are off by default. Turn them on with --provider azure or --provider all.
GitHub Action
# .github/workflows/llm-sunset.yml
name: llm-sunset
on:
push:
pull_request:
schedule:
- cron: "0 8 * * 1" # also re-check weekly: deprecations are announced while your code sits still
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: Ashveil1/llm-sunset@v0
with:
fail-within: 60 # optional
# provider: "openai anthropic"
# exclude: "tests/*"
# gitignore: "false" # scan git-ignored files too
Findings appear as inline annotations on the PR, along with a summary table on the run page.
pre-commit
repos:
- repo: https://github.com/Ashveil1/llm-sunset
rev: v0.2.0
hooks:
- id: llm-sunset
GitHub code scanning (SARIF)
- run: pipx run llm-sunset --format sarif --no-fail > llm-sunset.sarif
- uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: llm-sunset.sarif
Where the data comes from
Deprecation data comes from deprecations.info (source, MIT). It scrapes the official deprecation pages of OpenAI, Anthropic, Google Gemini and Vertex AI, AWS Bedrock, Azure AI Foundry, Cohere, Groq and xAI every day. llm-sunset caches it for 24 hours in ~/.cache/llm-sunset/ and falls back to a bundled snapshot that is refreshed weekly.
If you find a missing or wrong entry, please report it upstream at deprecations-rss. For false positives or negatives in matching, open an issue here.
Support the project
If llm-sunset saved you from a production outage, please consider sponsoring ❤️
License
MIT
Metadata
Release files for llm-sunset 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llm_sunset-0.2.0.tar.gz | 29.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llm_sunset-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.0 kB
Release files / llm_sunset-0.2.0.tar.gz
| Download URL | llm_sunset-0.2.0.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99861680e4a2a2fbe9e85a16a19f740753a4d51f454c7a4ce187fc95db1fc0d1
|
|
BLAKE2b-256 checksum How to use checksums |
dc77fd6456644731900d1398a16c8bbb9af1691b580ca5b253c836a67d442af0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logRelease files / llm_sunset-0.2.0-py3-none-any.whl
| Download URL | llm_sunset-0.2.0-py3-none-any.whl |
|---|---|
| Size | 25.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38916519e825f853cd4c1c0bd646617325294105559fe9489ec6a227ee896233
|
|
BLAKE2b-256 checksum How to use checksums |
fc3e5e79bf5f5a9a7faa690a043efd2e26720ae0f3f4df8c4bc76bec9ac73834
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency log