Dependency-change radar
package.json. See what already broke.In about 60 seconds, ChangelogRadar checks every dependency in your stack against our backfilled archive of API deprecations and vendor price changes — and tells you, plainly: which of your deps already shipped a breaking change, and which vendors quietly raised their prices. No signup. Just the verdict on the stack you're actually running.
No account. No email. Paste · scan · verdict in ~60s.
The free blast-radius scan
We read dependency names and versions only — no signup, no source code, nothing pushed to your repo.
We read dependency names + versions only. No signup, no source code, nothing pushed to your repo.
Here's what already happened to your stack.
0
of your 0 deps shipped a breaking change
0
vendors raised prices in the window
The concrete, sourced examples:
The scan above is a snapshot of the past. The Sunset Calendar is the live watch: an auto-updating .ics feed + Slack/email reminders for every upcoming deprecation and price change across your exact stack. Free tier can't replicate it — it isn't a snapshot, it's a watch.
One click. We create your account from checkout, lock your stack to the calendar, and the reminders start the same day.
The gap nobody owns
Stripe, Twilio, OpenAI, Auth0, SendGrid, Algolia, a payments gateway, three SDKs you forgot you installed. Each ships changes on its own schedule, on its own changelog, in its own tone — and none of them are reading your codebase to figure out whether this change touches you.
A 410 Gone in production, traced back to an endpoint a vendor sunset three weeks ago — in a changelog entry nobody on your team ever saw.
A provider moved to per-seat pricing and the only notice was a line in a blog post. You found out when the invoice arrived.
A deprecation warning you did see, six months ago, filed under "deal with it later" — 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. Not because anyone is careless — because manually reading 30 changelogs every week is a job nobody has, and RSS gives you everything except the one thing that matters: does this affect my stack?
ChangelogRadar closes that gap in two moves: first, it shows you what already broke in the stack you paste in. Then it makes sure you never get blindsided by the next one.
What's in the radar
Every change across your stack arrives pre-classified, dated, and sourced. You read four words and know whether to care.
Every change arrives pre-classified — Breaking, Deprecation, Price-change or Routine — with a sunset date and an explicit action required flag where it matters. Routine stays quiet; Breaking gets loud.
A live calendar of every upcoming deprecation and price change for your declared vendors. Subscribe the team to the .ics feed once; reminders fire ahead of each sunset so a deprecation becomes a planned ticket, not a 2 a.m. page.
Import your package.json and ChangelogRadar pins your exact versions. From then on it only flags changes that touch the versions you actually run — semver-aware, not "every Stripe change ever."
See what each vendor's pricing has actually done over time — every tier change, every per-unit bump, dated and sourced. Walk into the renewal conversation with the receipts instead of a vibe.
No change ships from us without a link to the vendor's own changelog and a date or sunset window. When we're not sure, we say so — "low confidence: vendor hasn't confirmed a date yet" — rather than fake an all-clear. The trust is the product.
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. Team plan pipes both to a webhook so it lands in the channel you already watch.
How the scan works
They finish in about a minute. The third is the thing a one-time scan structurally can't give you.
package.jsonDrop in your dependency manifest (or just the dependencies block). Nothing leaves to sign up; nothing hits your repo. We read the names and the versions you've pinned — stripe@12.4.0, twilio@4.x — and nothing else.
ChangelogRadar resolves each dependency against our archive of deprecations and price changes, version by version, then renders the verdict in plain language — the count, the classifications, and one concrete, sourced example. Enough to know it's true.
The scan tells you what already broke. The Sunset Calendar tells you what's about to — for your exact stack, before it pages you. A live .ics feed plus Slack and email reminders ahead of each sunset date. It isn't a snapshot — it's a watch, and the window moves with you.
Pricing
The scan and the public archive cost nothing; the recurring watch on your exact stack is the line.
Look at what already happened.
package.json, get the verdict (no signup)Never get blindsided again.
.ics + Slack/email remindersFor the 2–15 person eng team.
All plans: cancel anytime, self-serve in the billing portal. Annual billing saves ~2 months.
Straight answers
package.json; we match every dependency against our archive and return a verdict — how many of your deps have 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.coverage pending flag — never a false "all clear" — and every item is sourced and dated so you can verify us, not trust us blindly. 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 — that's years of vendor history, and it's what makes your scan and your calendar accurate today, not in six months..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. Cancel anytime, self-serve, no email-us-to-leave nonsense.Stop finding out from production
The signal is already public. The only question is whether you see it on a calendar — or in a stack trace. Paste your package.json. See what already broke. ~60 seconds, no signup.
412 vendors tracked · sourced to every vendor's own changelog · dated to the day