// Dependency-change radar
Paste your package.json.
See what already broke.
In about 60 seconds, ChangelogRadar checks every dependency against our backfilled archive of API deprecations and vendor price changes — and tells you, plainly: which deps already shipped a breaking change, and which vendors quietly raised prices. No signup. No card.
changelogradar — blast-radius scan
archive online25 vendors tracked·deprecations + price changes, dated to the day·sourced to every vendor's own changelog
// archive/sunsets.log
The archive already logged these.
A live tail of real vendor sunsets — every one dated and linked to the vendor's own notice. This is what your scan matches against.
- sourceDEPRECATIONStripeupcoming
Sources API deprecated in favor of PaymentIntents & PaymentMethods
- sourcePRICE ↑MongoDB
Atlas M2/M5 shared clusters replaced by Flex tier
- sourceBREAKINGTwilio
Programmable Chat / older messaging endpoints reach end of life
- sourceDEPRECATIONAWS SDK
AWS SDK for JavaScript v2 entered maintenance mode; end of support set
- sourceBREAKINGGoogle Cloud / Firebase
Firebase Dynamic Links shut down
- sourceDEPRECATIONVercel
Node.js 16 & 18 runtimes deprecated for Functions
- sourceDEPRECATIONAnthropic
Claude 1 & 2 models retired; migrate to Claude 3/4 family
- sourceDEPRECATIONNode.js
Node.js 18 reaches end-of-life
- sourceDEPRECATIONShopify
REST Admin API marked legacy; GraphQL is the primary API
39 dated changes in the archive · we link, we never reproduce.
// the gap
You don't build on one API anymore. You build on thirty.
Each ships changes on its own schedule, on its own changelog, in its own tone — and none of them read your codebase to check whether this change touches you. So it lands the way it always lands:
410 Gone in production — traced to an endpoint a vendor sunset three weeks ago — in a changelog nobody on your team ever saw.
invoice up 40% — a provider moved to per-seat pricing and the only notice was a line in a blog post.
“deal with it later” came due — a deprecation warning you did see, six months ago — and later turned out to be today, in prod, on a Friday.
Most teams find out their dependency changed when it breaks or when the invoice arrives — because reading 30 changelogs a week is a job nobody has. ChangelogRadar closes that gap: first it shows what already broke in the stack you paste, then it makes sure you never get blindsided by the next one.
// how it works
Three stages. The first two are free.
$ cat package.json | changelogradar scan | --watch
cat package.jsonPaste your package.json.
Drop in your dependency manifest — or just the dependencies block. Nothing hits your repo; we read names and pinned versions only.
changelogradar scanWe match it against the archive.
Every dependency is resolved against our backfilled archive of deprecations and vendor price changes, version by version. Free verdict in ~60s.
--watchTurn on your Sunset Calendar.
The scan tells you what already broke. The Sunset Calendar tells you what's about to — for your exact stack, on an auto-updating .ics feed with reminders.
// what you get
A vigilant newsroom for your dependencies.
- triage
Curated triage, not a firehose
- Every change arrives pre-classified — Breaking, Deprecation, Price-change, or Routine — with a sunset date and an action-required flag where it matters. We'd rather under-alert than cry wolf.
- sunset-calendar
The Sunset Calendar (.ics + Slack/email)
- A live calendar of every upcoming deprecation and price change for your declared vendors. Subscribe once; reminders fire ahead of each sunset. Auto-updates as vendors announce — you maintain nothing.
- stack-import
Stack import — paste once, watch forever
- ChangelogRadar pins your exact versions and only flags changes that touch the versions you actually run — semver-aware, not every Stripe change ever.
- provenance
Sourced and dated — every single item
- No change ships from us without a link to the vendor's own changelog and a date. When we're not sure, we say so — a green all-clear only means something because we never bluff one.
- alerts
Instant alerts + weekly digest
- A calm weekly digest of everything that moved in your stack, plus instant alerts the moment a Breaking change or price hike lands on a vendor you depend on.
- pricing-history
Pricing-history charts
- See what each vendor's pricing has actually done over time — every change, dated and sourced. Walk into the renewal with the receipts instead of a vibe.
// in practice
What it feels like.
I pasted our package.json expecting nothing. It came back with two breaking changes already shipped and a Twilio endpoint we were still calling. The free scan paid for the subscription before I'd even signed up.
We used to find out about deprecations from a failing build. Now they're calendar invites with 30 days of runway. The Sunset Calendar turned 'oh no' into a backlog ticket.
The pricing-history chart alone won us a renewal negotiation — I walked in with three years of a vendor's price changes, dated and sourced.
// plans
Free to look. One price to be warned ahead of time.
The blast-radius scan and the public archive cost nothing. You only pay for the recurring watch on your exact stack — the Sunset Calendar the free tier structurally can't replicate. Flat pricing, cancel anytime.
Free
readLook at what already happened.
- Full public archive — every tracked deprecation & price change, searchable
- Free stack blast-radius scan — paste package.json, get the verdict (no signup)
- Free Watch: up to 3 vendors
- Weekly change notifications for your 3 declared vendors
Pro
watchNever get blindsided again.
or $240/yr — 2 months free
Turn on my Sunset Calendar- Unlimited vendors — watch your whole stack, not just 3
- The Sunset Calendar — auto-updating .ics feed + Slack/email reminders
- Instant alerts on Breaking changes & price hikes the moment they land
- Weekly digest of everything that moved in your stack
- Stack import from package.json — semver-aware, version-pinned
- Pricing-history charts for every vendor you depend on
Team
teamFor the 2–15 person eng team.
or $490/yr — 2 months free
Start the team watch- Everything in Pro
- Webhooks — pipe alerts & digests into Slack/Discord/your endpoint
- 5 seats — your whole engineering team on one watch
- API access — query the change archive & your stack programmatically
- Priority coverage — request a vendor and we backfill it first
All plans: cancel anytime, self-serve in the billing portal. Annual billing saves ~2 months.
Frequently asked questions
What exactly does the free scan show me — and what does it cost?
Nothing, and no account. You paste your package.json; we match every dependency against our archive and return a verdict — how many of your deps already shipped breaking changes, how many vendors raised prices in the window, and one concrete, sourced example. The free scan is a snapshot of the past. The Sunset Calendar — the live watch on upcoming changes for your exact stack — is the paid part, because that's the value that recurs.
Is $24 flat, or does it scale with my stack?
Flat. Pro is $24/mo for unlimited vendors — 8 APIs or 40, the price doesn't move. We don't meter per-vendor or per-alert. Team is a flat $49/mo for 5 seats, webhooks, and API. Annual on either runs ~2 months free.
Do you send my code or package.json anywhere? Is my stack private?
We read dependency names and versions — never your source. Your declared stack is stored under row-level security, used only to compute your alerts and calendar, and never sold, pooled, or shown to anyone else. The public archive is built from vendors' own changelogs, not from customers' manifests.
Isn't this just an RSS reader or a Dependabot I could set up myself?
RSS gives you every change from every vendor and leaves the filtering — the actual work — to you. Dependabot watches package versions, not vendor changelogs, deprecations, or pricing. ChangelogRadar reads the firehose, classifies each change (Breaking / Deprecation / Price-change / Routine), matches it against the exact versions you run, and only pings you for the ones that touch your code — with the upcoming ones on a calendar before they break.
What stops you from missing a change, or a competitor from cloning this?
On misses: for a vendor we don't track yet you see a coverage-pending flag — never a false all-clear — and every item is sourced and dated so you verify us, not trust us. On cloning: anyone can build a changelog reader; what's hard to copy fast is the backfilled archive of historical deprecations and price changes matched to specific versions.
What happens when I cancel?
You drop to Free: the public archive and the blast-radius scan stay available, and your Free Watch covers up to 3 vendors. Your Sunset Calendar .ics feed and instant alerts switch off, and stack import past 3 vendors pauses. No data is deleted; resubscribe and your watch resumes where it left off.
// stop finding out from production
The change already shipped. The only question is whether you see it on a calendar — or in a stack trace.
$ changelogradar --watch # never blindsided again
25 vendors tracked · sourced to every vendor's own changelog · dated to the day