Dependabot
5,546Automated dependency-update PRs that flag outdated and vulnerable packages.
Maturity tier details
Computed tier: 3(raw score 4). Effective tier: 3.
Facets:documented_in=0evaluated_on=0integration_surfaces=0.5paper_citations=0recent_commit=2stars=1.5
Source of truth:pipeline/maturity/score.py
Description
Automated dependency maintenance service integrated into GitHub. Monitors manifests (package.json, requirements.txt, go.mod, Cargo.toml, etc.) for outdated or CVE-affected versions and opens pull requests that bump to safe releases, with release notes and compatibility scores attached. Runs as a scheduled GitHub-hosted bot plus the open-source dependabot-core engine; PRs are reviewed and merged by humans, so mitigation is graduated-HITL even though scanning itself is autonomous.
Why it's included
Occupies detection x post_generation x graduated_hitl for the obsolescence failure mode: once code has shipped with a given pinned version, Dependabot watches the advisory feed and proposes upgrades for a human to merge. Distinctive for being the default, no-configuration-required option on GitHub, which makes it the most-deployed mitigation for stale dependencies in practice. Complements Renovate (same cell, more configurable) and context-hub (pre_generation prevention via fresh docs).
Security notes
Free for public and private GitHub repos; the hosted service runs in GitHub's infrastructure with repo read/write scopes. Dependabot-core itself is MIT-licensed and can be self-hosted. Fix PRs are signed by the Dependabot bot; review auto-merge policies carefully to avoid rubber-stamping malicious upstream releases masquerading as patch bumps.
Addresses failure modes
- 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.
- Security vulnerability — Insecure patterns, injection flaws, weak cryptography, secret leakage.