Safe to Upgrade? reads a repo's package.json, collects the breaking
changes for the target upgrade of each dependency, and deterministically searches the codebase
for real usage of the removed or renamed APIs. One verdict per package:
REVIEW (a breaking API is used, with file:line evidence),
SAFE (breaking-change data exists and none of its APIs are used), or
UNKNOWN (no breaking-change data — the tool says so instead of guessing).
Recorded demo — not a live backend. Every table and count on
this page is the recorded output of a real run of verdict.py: the sample-project
run stored in report.md / report.json and the real-world run stored
in realworld-report.md / realworld-report.json, both logged in the
project's EVALUATION.md. The data is embedded in this page exactly as those files
recorded it; nothing here executes the tool in your browser.
| Package | Upgrade checked | Verdict | Breaking APIs checked | Uses found |
|---|
Verdict meanings, as recorded in the run reports — REVIEW: “Breaking APIs are used — manual review before upgrading.” SAFE: “Breaking-change data exists, none of its APIs are used.” UNKNOWN: “No breaking-change data — not guessed.” Rows marked REVIEW can be clicked to expand their file:line evidence; any row can be clicked to see the reason the run recorded.