News for hackers. Stuff that matters.
Re:Vulnerability Management for Go by shp0ngle on Tuesday September 06, 2022 @12:16PM (#32739218)
go.mod IS a lockfile.

go.mod will exactly tell you what version you have, always. *

* that does not apply if your code is a library; then, other dependency of the "main" app can "update" your dependency. Which sometimes does break things.

However, the go.mod of the main app will deterministically tell what version is used, always.

I never did understand what packages go to go.sum though and what is the logic there. But it is not that important.

Re:Vulnerability Management for Go by preseinger on Tuesday September 06, 2022 @07:41PM (#32744592)
This is only true for go 1.17 and above. Prior to that, go.mod wouldn't necessarily list all transitive dependencies. And I don't think this property is actually guaranteed by the relevant specification. The only reliable way to get a "lock file" is to run go list. Unfortunately.
Re:Vulnerability Management for Go by indil on Friday September 09, 2022 @02:41PM (#32783246)
go.mod lists minimum versions. Minimum Version Selection may increase the versions used as required by other packages in the build. go.mod isn't a lock file.