All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Replacing Dependabot with Targeted GitHub Actions for Go Dependency Management

By

todsacerdoti

3mo ago· 9 min readenOpinion

Summary

The article argues that Dependabot, GitHub's automated dependency update tool, creates excessive noise and discourages more meaningful work, particularly for security alerts in the Go ecosystem. The author recommends turning off Dependabot and replacing it with two scheduled GitHub Actions: one running govulncheck for vulnerability scanning, and another running test suites against the latest dependency versions. The article includes a case study about a security fix for the filippo.io/edwards25519 library where the MultiScalarMult method produced invalid results when the receiver wasn't the identity point, illustrating the limitations of automated dependency management tools.

Key quotes

· 4 pulled
Dependabot is a noise machine. It makes you feel like you're doing work, but you're actually discouraging more useful work.
I recommend turning it off and replacing it with a pair of scheduled GitHub Actions, one running govulncheck, and the other running your test suite against the latest version of your dependencies.
The (*Point).MultiScalarMult method would produce invalid results if the receiver was not the identity point.
This is especially true for security alerts in the Go ecosystem.
Snippet from the RSS feed
I recommend turning Dependabot off and replacing it with a pair of scheduled GitHub Actions, one running govulncheck, and the other running CI against the latest version of your dependencies.

You might also wanna read