Renovate
23,220Highly configurable multi-platform dependency update bot.
Activity band details
Activity band A to F: a bin of a score that adds GitHub stars (log scale), a push to the upstream repository in the 12 months before `as_of`, the number of declared integration surfaces and, where the catalogue records them, citing papers and benchmark evaluations. It measures popularity and activity. It is not a level of evidence: no band means a paper cites the tool or that it was measured. Recency is judged as of 2026-11-22.
Computed band: C
(raw score 4.75).
Shown band: C
.
Facets:
documented_in=0evaluated_on=0integration_surfaces=1paper_citations=0recent_push=2stars=1.75
Source of truth: pipeline/maturity/score.py
Description
Open-source dependency-update bot from Mend (formerly WhiteSource) that scans repositories across GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea, then opens PRs/MRs to bump outdated packages. Supports 90+ package managers and offers fine-grained config for grouping, scheduling, automerge rules, and vulnerability-only alerts via a JSON/JSON5 renovate.json file. Self-hostable as a CLI or Docker image; a hosted Mend Renovate App is also available for GitHub.
Why it's included
Occupies detection x post_generation x graduated_hitl alongside Dependabot but with config-first ergonomics and cross-forge reach (GitLab, Bitbucket, Azure DevOps), filling the same cell for teams that are not on GitHub or need update-grouping that Dependabot does not express. Its broader manager coverage (Terraform, Helm, GitHub Actions digests) extends obsolescence mitigation into infrastructure-as-code manifests that pure application-package tools miss.
Security notes
AGPL-3.0 core; the Mend-hosted app adds proprietary enrichment. Bot runs with repo write scope to open PRs; self-hosted deployments keep manifest data on-prem. Automerge configurations must be scoped (e.g., devDependencies patch only) so that compromised upstream releases are not merged without human review - the same supply-chain caveat applies as with any auto-updater.
Addresses failure modes
These tags are the catalog's claim about what Renovate is built to catch or prevent. A tag is not a test result. SAICA-Bench has not measured Renovate, so none of these tags is tested here.
- Obsolescence — Using deprecated APIs, retired packages, or outdated library versions — often because the model's training data pre-dates current releases.
- Supply-chain attack — Slopsquatting, typosquatting, compromised MCP servers.