Open mewmew opened 1 year ago
Thanks! Having smooth workflows for just this kind of use-case is definitely something we're working on.
Thanks! Having smooth workflows for just this kind of use-case is definitely something we're working on.
Hi John,
That's wonderful to hear!
Really glad to see such an active effort towards mitigating potential supply chain attacks. It's vital for the health of the Go open source ecosystem.
With kindness, Robin
Hi! I'm interested on this too. Is there any WIP code for this feature available?
First off, really happy to see the birth of the
capslock
tool as having a way to track capabilities used by transitive dependencies is key to mitigating supply-chain attacks.One feature that would be really incredible to incorporate in
capslock
and associated tools is to easily diff the capabilities added/removed in between two versions of a given Go module/package.And furthermore, make it possible to hook this functionality up to
go get -u
.Imagine being able to run
go get -u ./...
to update packages of a Go module and having warnings be emitted for newly added capabilities of transitive dependencies.E.g.
Of course, neither
go get
norcapslock
need to perform the capability diff itself, it could be a third glue tool that reads the versions (of updated dependencies) fromgo get -u
and the json output of capabilities ofcapslock
and prints warnings for newly added capabilities.Once more, thanks for working to improve this space and help regain confidence in the capabilities utilized by dependencies in the open source community.
With cheerful regards, Robin