Ripedeps

Recommends version upgrades for a package.json: the newest versions that are old enough and within the allowed step size, kept aligned with each other (peer dependencies and the first-level dependencies of the packages). Deterministic, no AI. Returns the new package.json, a unified diff (apply with `patch -p1`) and a per-package table with the reasons. Every package has an `explanation` sentence and `notes` lists other changes to the file (the `ripedeps` entry): relay them to the user as the rationale for each change. Send the file as `packageJson` (text) or as `packageJsonUrl` (https URL of a raw file), exactly one of them. Recommended: minAgeDays 7 (versions younger than 7 days are not proposed). The default is 0, or the `ripedeps` entry of the file. maxBump defaults to minor. Use `focus` to restrict the upgrade to some packages (and their direct neighbours). Try more than one level: a plan only suggests and writes nothing, so calling again is cheap. Start with minor; if a package is held with a `level-limit` reason (a newer major exists), call again with maxBump "major" (optionally with `focus`) and compare. A `held` result is a reasoned decision for that one package, not a ban on the level: its reason names what blocks it (a peer or dependency constraint). Apply a larger step only when the user approves it. Privacy: We do not keep your package.json: every upload is processed from scratch and discarded, nothing about its content or your IP address is remembered. Only anonymous statistics (file size, number of dependencies, number of changes) are counted.