Skip to content

ci: check dependencies with gosocialcheck - #53979

Open
AkihiroSuda wants to merge 1 commit into
moby:masterfrom
AkihiroSuda:gosocialcheck
Open

AkihiroSuda wants to merge 1 commit into
moby:masterfrom
AkihiroSuda:gosocialcheck

Conversation

@AkihiroSuda

@AkihiroSuda AkihiroSuda commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

Summary

Run gosocialcheck to check whether the dependencies of the main module, api, and client are adopted by trusted projects (i.e., CNCF graduated projects).

Findings are reported as GitHub Actions annotations on go.sum and do not fail the job.

Docker, Moby, and golang.org/x packages are annotated as trusted (//gosocialcheck:trusted) in go.mod.

https://github.com/AkihiroSuda/gosocialcheck

See:

Release notes (optional)

A picture of a cute animal (not mandatory but encouraged)


Created with: Claude Code

Comment thread client/go.mod Outdated
Comment on lines +28 to +33
// Docker, Moby, and golang.org/x packages are trusted
//gosocialcheck:trusted
require (
github.com/moby/docker-image-spec v1.3.1 // indirect
golang.org/x/sys v0.33.0 // indirect
)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this something that can be configured through other ways? If I'm not mistaken, go (finally!?) started fixing grouping in go.mod to prevent multiple groups (multiple direct / indirect).

Also slightly wondering what makes decisions in CNCF projects more trust-worthy than (e.g.) moby itself? (I've seen some poor choices and messy dependency-management in CNCF)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this something that can be configured through other ways?

Updated to use inline comments instead of require() group comments

If I'm not mistaken, go (finally!?) started fixing grouping in go.mod to prevent multiple groups (multiple direct / indirect).

Yes, seems started in Go 1.27 😞

Also slightly wondering what makes decisions in CNCF projects more trust-worthy than (e.g.) moby itself?

s/CNCF projects/CNCF graduated projects/
s/more/same/

(I've seen some poor choices and messy dependency-management in CNCF)

https://github.com/cncf/toc/blob/main/.github/ISSUE_TEMPLATE/template-graduation-application.md#security could be improved?

Comment on lines +259 to +261
name: Install gosocialcheck
run: |
go install "github.com/AkihiroSuda/gosocialcheck/cmd/gosocialcheck@${GOSOCIALCHECK_VERSION}"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this run as linter in golangci-lint? Similar to (e.g.) forbidigo ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure, as gosocialcheck is a linter for go.mod rather than Go source codes themselves.
Could be experimented as a plugin anyway

Run gosocialcheck to check whether the dependencies of the main
module, api, and client are adopted by trusted projects (i.e., CNCF
graduated projects).

Findings are reported as GitHub Actions annotations on go.sum and do
not fail the job.

Docker, Moby, and golang.org/x packages are annotated as trusted in
go.mod.

https://github.com/AkihiroSuda/gosocialcheck

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci kind/enhancement Enhancements are not bugs or new features but can improve usability or performance. meta/ai-assisted module/api module/client

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants