Skip to content

Disabling Go dependency graph data #265

Closed
0 of 2 issues completed
Closed

Description

@nickyringland

As part of our ongoing work ensuring and improving data quality, we have run into issues with generating the Go dependency graphs. Unfortunately, our graphs for Go are not at the quality that we expect and feel confident publishing. As such, we will be disabling Go dependency graphs.

Dependency graphs are complex and especially complex when computing at an ecosystem level! We don’t currently see extensive usage of our Go dependency data, so we don’t expect this to have a major impact on our users. Historical graphs will still be available through the BQ Dataset. And, as always, please get in touch with us if you have feedback.

We are working on a new solution for providing transitive dependency information for Go modules, so stay tuned.

Activity

  1. hahaxixihaha commented on Jun 19, 2025

    @hahaxixihaha

    Hi, is there any lightweight way to get downstream dependents for Go modules now that the graphs are disabled? BigQuery queries are too expensive.

    For example, I’d like to check which projects depend on github.com/corazawaf/coraza/v3 at version v3.3.2.

    Thanks!

  2. nickyringland commented on Jun 24, 2025

    @nickyringland
    CollaboratorAuthor

    @hahaxixihaha Unfortunately there's no way to do this at the moment, (other than by using the BigQuery historical data, which as you mention can be expensive to query). But we're working on bringing this functionality back, and will update here when we have more details.

  3. hahaxixihaha commented on Jun 27, 2025

    @hahaxixihaha

    @hahaxixihaha Unfortunately there's no way to do this at the moment, (other than by using the BigQuery historical data, which as you mention can be expensive to query). But we're working on bringing this functionality back, and will update here when we have more details.

    Ok then. Thank you very much and I'm looking forward to your good news!

  4. pxp928 commented on Jul 1, 2025

    @pxp928

    @nickyringland looks like the API (v3Alpha) is still responding to dependency queries. Will that also get disabled soon? Will the new solution provide API access to the dependencies also?

  5. NorthWindH commented on Jul 4, 2025

    @NorthWindH

    Hey @nickyringland just commenting to register that I use the dependency graph data for go quite a bit, especially the "dependents" tab, when evaluating libraries. I know that I can get similar data from go.pkg.dev itself but your ui is much nicer to look through.

    I know you probably have metrics to assess product decisions but I'm hoping that this comes back online soon as it was quite nice; even presenting the same data as returned by go mod graph would be great :)

  6. liavyona commented on Jul 14, 2025

    @liavyona

    +1 on fixing that

  7. liavyona commented on Jul 14, 2025

    @liavyona

    Also, I think it is worth updating the docs

    Image
  8. shanigold1 commented on Jul 14, 2025

    @shanigold1

    +1 on fixing that

  9. OmerYa commented on Jul 14, 2025

    @OmerYa

    +1 on fixing that.

  10. xxLiuxx commented on Mar 4, 2026

    @xxLiuxx

    Hi @nickyringland , I just wanna follow up and check if there's an estimated timeline for this refactoring? Thanks

  11. nickyringland commented on Jun 10, 2026

    @nickyringland
    CollaboratorAuthor

    The Go transitive dependencies are available via the GetRequirments API. We also have dependencies available for all other ecosystems via GetRequirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ANNOUNCEMENTgoPull requests that update Go code

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions