Extract Dependency Data on Scale with Renovate
summary
Renovate extracts concrete dependency data at scale by running managers for Dockerfiles, NPM, PDM, Terraform, GitHub Actions and many custom formats and emitting structured JSON reports or pushing to S3 for analysis. It supports over 65 data sources and 100+ managers, offers dry run modes extract/lookup/full, and configurable options like requireConfig, force and forkProcessing. A Backstage integration runs Renovate horizontally as a Backstage plugin and at N26 it collects about 44,000 tracked items with ~400,000 historical datasets, and it works in production.
AI-written summary · about
chapters (13)
- 0:00Renovate and dependency challenges
- 1:03Why dependency data matters at scale
- 7:14What Renovate is and how it works
- 10:48Custom managers and internal deps
- 14:40Three ways to extract dependency data
- 18:11Renovate reports for large-scale analysis
- 25:02Tools built on Renovate for insights
- 29:06Live demo with Backstage
- 35:14N26 use case with 400k datasets
- 37:49Limitations and future of extraction
- 41:04Configuring Renovate workflow
- 45:31Caching strategies and registry efficiency
- 46:13Q&A
related talks
33mUsing Renovate to keep your version dependencies updated
05mQuantifying your reliance on Open Source software
30mDependency management: the cause of—and solution to—all supply chain problems
23mSupply Chain Security using Free and Open Tools
32mLet's pin that dependency
17mBuilding Secure Open Source Communities From the Ground Up
44mBridging Open Source Developer Platforms: Backstage Meets Coder
01h 01mAutomating dependency selection with open-source tools at scale