Skip to content

No vulnerabilities reported for quic-go@0.40.0 in v3 API #2334

Open

Description

@lamppu

Hi! The v1 API reports a vulnerability (CVE-2023-49295) for the pkg:golang/github.com/quic-go/quic-go@0.40.0 package, but v3 API doesn't. Not sure if this is related to the importer issues regarding Go packages in general, but reporting anyway because of the discrepancy.

Activity

  1. TG1999 commented on Jun 11, 2026

    @TG1999
    Contributor

    @lamppu thanks for bringing this up, golang packag type is not supported as of now in V3, it will be supported in future. Thanks!

  2. sschuberth commented on Jul 3, 2026

    @sschuberth

    it will be supported in future.

    Any timeline for that? As API v1 is now gone in the public instance running at version 40.0.0, this is a breaking change for anyone interested in Golang vulnerabilities.

  3. TG1999 commented on Jul 16, 2026

    @TG1999
    Contributor

    The current golang PURL type:

    • Uses the import path split into namespace (all but the last segment) and name (last segment).
    • Predates Go modules and therefore cannot reliably distinguish modules from packages in modern Go projects.
    • Works well for older GOPATH-style code but is imperfect for today's module-based ecosystem, where correctly identifying a module often requires consulting go.mod files or a Go module proxy.

    So we will use the current golang spec https://github.com/package-url/purl-spec/blob/main/types/golang-definition.json and will go with the approach of taking last segment of the import path as name and rest as namespace

  4. TG1999 commented on Jul 18, 2026

    @TG1999
    Contributor

    We will not ingest data from gitlab and github, we will have a new pipeline based on https://github.com/golang/vulndb and the PURL will be formed like this example

    for go.woodpecker-ci.org/woodpecker/v2 : pkg:golang/go.woodpecker-ci.org%2Fwoodpecker/v2

  5. TG1999 commented on Nov 3, 2026

    @TG1999
    Contributor

    WIP #2491

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions