You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
rsc.io/pdf never shows up in the actual import graph for this repo:
$ go mod why rsc.io/pdf
# rsc.io/pdf
(main module does not need package rsc.io/pdf)
It is used during module version resolution, which is why it shows up the go mod graph output. I don't think these types of "resolution only" packages should show up in an SBOM. It's difficult to do this right, so I want to first discuss here before starting on any code.
The text was updated successfully, but these errors were encountered:
The command here returns too many modules, including some that never make it into the compiled code: https://github.com/spdx/spdx-sbom-generator/blob/master/internal/modules/gomod/handler.go#L86
You can see it for this repo itself:
rsc.io/pdf never shows up in the actual import graph for this repo:
$ go mod why rsc.io/pdf # rsc.io/pdf (main module does not need package rsc.io/pdf)
It is used during module version resolution, which is why it shows up the go mod graph output. I don't think these types of "resolution only" packages should show up in an SBOM. It's difficult to do this right, so I want to first discuss here before starting on any code.
The text was updated successfully, but these errors were encountered: