Deprecation data your scripts and CI can read.
Changes.Watch publishes a free JSON catalog of confirmed software deprecation signals. Use it for internal tooling, monitoring experiments, research, or the first layer of a repository scanner.
Fetch the complete v1 snapshot
Authentication is not required. The endpoint supports browser requests, CDN caching, ETags, and conditional requests.
curl --fail --etag-save catalog.etag --etag-compare catalog.etag \ https://www.changes.watch/api/v1/deprecations/catalog.jsonStable identifiers and official sources
schemaVersionMajor response contract version. Additive fields may appear within v1.
generatedAtTime when the cached JSON snapshot was generated.
updatedAtNewest announcement timestamp, or null for a valid empty catalog.
catalogVersionSHA-256 identifier for the ordered notice content.
notices[].idStable public identifier based on the public update slug.
productPublic product slug and display name.
announcementAtWhen the vendor deprecation announcement was published.
componentHuman-verified affected component, or null when it has not been curated.
effectiveOnVendor-stated effective calendar date, or null when unknown.
replacementOptional human-verified replacement guidance.
packageTargetsVerified npm package/range targets; empty when no exact mapping is known.
aliasesVerified npm package-to-product mappings for scanner discovery.
officialSourceUrlOriginal vendor changelog, documentation, or announcement.
changesWatchUrlCanonical Changes.Watch detail page for the notice.
{
"schemaVersion": 1,
"generatedAt": "2026-07-31T10:00:00.000Z",
"updatedAt": "2026-07-30T14:00:00.000Z",
"catalogVersion": "sha256:…",
"total": 1,
"notices": [
{
"id": "cw-deprecation:example-api-deprecation",
"product": { "slug": "example", "name": "Example" },
"title": "Legacy API is deprecated",
"announcementAt": "2026-07-30T14:00:00.000Z",
"summary": ["Migrate to the current API."],
"severity": "Risky",
"tags": ["breaking", "deprecation"],
"officialSourceUrl": "https://example.com/changelog/…",
"changesWatchUrl": "https://www.changes.watch/updates/…",
"component": { "kind": "package", "name": "Legacy client SDK" },
"effectiveOn": "2026-12-31",
"lifecycleStatus": "active",
"replacement": "Migrate to @example/current-client.",
"migrationUrl": "https://example.com/migrate",
"verifiedAt": "2026-07-31T10:00:00.000Z",
"packageTargets": [
{
"ecosystem": "npm",
"package": "@example/legacy-client",
"affectedRange": "<4.0.0",
"targetKind": "direct",
"replacementPackage": "@example/current-client"
}
]
}
],
"aliases": []
}Structured matching without invented facts.
The current catalog includes deprecation notices already published by Changes.Watch. Human-verified notices can additionally publish affected components, effective dates, replacements, migration URLs, and npm package ranges. Legacy or not-yet-curated notices keep these fields null or empty; the API never invents them from prose.
Built in public for developer workflows.
The existing ChangesWatch organization is the public home for upcoming developer integrations. Public repositories will appear there as they are ready. The roadmap starts with this catalog, then adds a manifest scanner, a simple GitHub Action, and an opt-in GitHub App for periodic repository checks.
github.com/ChangesWatch
Follow all public Changes.Watch tools and repositories.
Scanner → Action → GitHub App
Each public repository will include installation instructions, security policy, versioned releases, and a clear support status.
A GitHub Action will turn this catalog into repository checks.
The reserved identifier is ChangesWatch/deprecation-scan@v1. The Action is not installable yet; read the public contract, permissions, privacy model, and planned workflow examples before the beta release.