Paranoid by default

Paranoid
dependency
updates.

A Renovate-compatible bot that waits until an update has aged into safety — then opens the PR. Keep your renovate.json, swap the bot.

Dependency Dashboard craftlions/uppy
# Detected updates
[ ]  npm  node             20.11.0 → 20.11.1   held 2d · aging
[x]  mise aqua:aws/aws-cli  2.15.0 → 2.15.4    safe · 3d ✓ PR #42
[x]  gha  actions/checkout  @<sha> # v4.1.0   pinned ✓
01 / Why wait

A version is most dangerous the day it ships.

A hijacked publish token, a compromised maintainer, a malicious post-install script — supply-chain attacks live in the first hours of a release, before anyone has looked. Most update bots open the PR the moment the version appears, racing you straight into the blast radius.

uppy refuses to. It treats age as evidence: a release has to survive in the wild long enough for the ecosystem to notice if something is wrong. Only then does it count as an update worth recommending.

02 / Paranoid safety

Two rules uppy enforces no matter what your config says.

Renovate makes these optional. uppy makes them non-negotiable — if your config asks for less, uppy ignores it.

Minimum release age

A 3-day floor, always

uppy will not recommend a version until it has been published for at least three days. Set a shorter cooldown in config and it makes no difference — the paranoid floor wins. Time in the wild is the cheapest safety check there is, so uppy never skips it.

Digest pinning

The sha is the ground truth

Every unpinned GitHub Action gets pinned to the exact commit sha its tag resolves to — @<sha> # v4.1.0. The trailing comment is attacker-controllable, so uppy never trusts it: it reverse-resolves the sha to a tag, because the sha is what GitHub actually checks out.

And it watches for known vulnerabilities.

Age and pinning guard against the unknown. Advisories cover the known — surfaced right on the Dependency Dashboard, with more on the way.

Available now

OSV + GitHub alerts

uppy queries the OSV database for your npm dependencies and reads GitHub and Dependabot security advisories, flagging every affected package directly on the Dependency Dashboard.

Advisories Coming

Snyk & more sources

More advisory feeds — Snyk and others — layered on top of OSV and GitHub, so a vulnerability flagged anywhere gets caught here.

AI threat scan Coming

Reads the source diff

AI reads the actual code changes between your installed version and the proposed one, flagging suspicious additions — new network calls, obfuscation, install scripts — before the update reaches you.

03 / Renovate-compatible

Keep the config you already wrote.

uppy reads your existing Renovate configuration and manifests as-is. There is nothing to port and no new schema to learn — point it at a repo and it speaks the vocabulary you already know.

  • Managers detect your manifests — npm, mise, github-actions.
  • Datasources resolve versions — matchDatasources works the way you expect.
  • Versioning classifies bumps with the same semver rules.
  • Everything surfaces on a familiar Dependency Dashboard.
renovate.json
{
  "extends": ["config:recommended"],
  "packageRules": [
    {
      "matchManagers": ["npm"],
      "matchDatasources": ["npm"]
    }
  ]
}

No migration. uppy adds its paranoid floor on top.

uppy config Coming

Or graduate to uppy.jsonc

Stay on renovate.json as long as you like — uppy reads everything it supports. When you want less boilerplate and paranoid defaults built in, migrate to a native uppy.jsonc. Once you do, uppy reads it instead and your Renovate config steps aside.

04 / Supported managers

Covers the stack you actually run.

npm

package.json

Dependencies and devDependencies resolved through the npm Datasource, with plain semver versioning.

mise

mise.toml

One Manager across every backend — core:node, aqua:aws/aws-cli, github:endevco/aube, npm:@openai/codex — each routed to the right Datasource.

github-actions

workflow files

Actions resolved via github-tags, tolerant of a leading v — and pinned to their sha by default.

05 / Smarter updates

Updates that arrive pre-triaged.

Paranoia decides what is safe to update. Next, uppy uses AI to make the safe updates easier to act on — without ever taking the human out of the loop.

Summaries Coming

Knows what changed

AI distills the changelog, release notes, and commits into a short, honest summary of what an update actually does — so you are not reading upstream history yourself.

Relevance Coming

Sorted by what matters to you

AI reads what your project is and ranks the queue accordingly. In an Astro-on-Cloudflare app, an astro or Cloudflare bump outranks a dev-only CLI — urgent and central first, trivial last.

Codemods Coming

Fixes breaks before you look

When an update would break your code, AI attempts the fix on the PR branch so it builds — and tells you what it could not. A human always reviews and merges; uppy never merges on its own.

06 / Fast & free

Fast by architecture. Free under fair use.

uppy runs on Cloudflare Workers and Workflows, at the edge. Update checks fan out their Datasource lookups in parallel, and every safe upgrade runs the full clone → update → commit → push → PR cycle inside its own isolated e2b sandbox.

No heavyweight runner to babysit, no queue to wait behind. When uppy launches it will be free under a fair-use policy — normal, personal, and open-source use at no cost.

Stop updating on release day.