How to measure dependency lag across your repositories
Dependency lag is how far your pinned versions trail the latest releases. Here is a practical way to measure it per repo, track it over time and act on it.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Dependency lag is how far your pinned versions trail the latest releases. Here is a practical way to measure it per repo, track it over time and act on it.
Hash-checking mode makes pip refuse any download that does not match a hash you recorded. How to enable it, what it requires, and what it cannot prove.
Run the scan on every pull request, name the job, then mark it as a required status check in branch protection. Steps, pitfalls, and what skipped means.
Five settings a small team can change this week to reduce GitHub Actions risk: token permissions, pinned actions, secrets, review and approvals.
Lock Java dependency versions with Gradle dependency locking or Maven dependencyManagement and the enforcer plugin so scans match what ships.
Turn on Gradle dependency locking, generate gradle.lockfile with write-locks, commit it, and update chosen modules on purpose. Steps and caveats inside.
IDE, CI and platform scans disagree when versions, databases, config or inputs differ. Align the scanner version, data build, policy and lockfile to match.
Pinning to a commit SHA stops silent changes but also stops updates. Dependabot can open pull requests for pinned actions. Setup and review habit.
Use per-tenant concurrency caps, fair queuing and quotas on expensive scan types so one busy monorepo cannot delay every other team's pipeline.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.