Since.dev

No reviews yet — be the first to review →

freemium • Free tier

Updated Sep 2026

Since.dev targets a failure mode every team recognises and few monitor: code that breaks without anyone committing anything. An endpoint is deprecated, an SDK changes a default, a model version is retired, a response shape gains a field — and software that worked yesterday starts failing. Dependency bots handle version bumps in your package manifest, but they say nothing about a hosted service changing behaviour behind a stable version number, which is where the painful outages live. Since monitors the external surfaces a repository depends on, assesses whether a given change actually affects your code paths, and prepares a targeted repair as a draft pull request. The design choice worth noting is where it stops: your existing CI runs against the change and your team decides what ships. Nothing merges itself. That keeps the tool useful in codebases where an automated commit would be unacceptable, and it means the output is reviewable in a workflow you already have rather than a new dashboard someone must remember to check. The honest caveats are about precision. Impact assessment is inference, so expect some noise — pull requests for changes that turn out not to matter, and occasionally a change that matters more than the diff suggests. Draft fixes are a starting point for a reviewer, not a merge-blind guarantee, and coverage depends on which providers and packages are supported, so verify your specific stack is watched before relying on it. Judged as a reviewer's head start on a class of breakage nobody currently owns, it is a sensible piece of infrastructure.