n8n - 💡(How to fix) Fix question on dependency surface area and triage cadence across integration packages [1 comments, 2 participants]

hi, we've been researching repo health across the open source ecosystem using a tool called repOptics. ran a scan on n8n and the overall profile is strong (B:80), but two things stood out: bloat scoring 55/100 and dependencies at 56/100. with 400+ integration nodes and 70+ CI workflows, n8n is clearly investing heavily in quality infrastructure. curious how the team thinks about the dependency surface area that comes with that many integrations. is there a triage cadence for dep updates across packages, or does the volume mostly flow through automated PRs?