Skip to content

License information inconsistently returned from version endpoint #1027

@garethr

Description

@garethr

It looks like some of the version endpoints return license information, while others do not. I noticed this with Go first:

$ http https://packages.ecosyste.ms/api/v1/registries/proxy.golang.org/packages/github.com%2Fspf13%2fcobra/versions/v1.7.0 | jq .licenses
null

$ http https://packages.ecosyste.ms/api/v1/registries/proxy.golang.org/packages/github.com%2Fspf13%2fcobra | jq .licenses
"Apache-2.0"

But i doesn’t seem to affect npm:

$ http https://packages.ecosyste.ms/api/v1/registries/npmjs.org/packages/penplot | jq .licenses
"MIT"
$ http https://packages.ecosyste.ms/api/v1/registries/npmjs.org/packages/penplot/versions/3.0.0 | jq .licenses
"MIT"

But does affect PyPI:

$ http https://packages.ecosyste.ms/api/v1/registries/pypi.org/packages/urllib3/versions/2.3.0 | jq .licenses
null
$ http https://packages.ecosyste.ms/api/v1/registries/pypi.org/packages/urllib3 | jq .licenses
"MIT License"

I'd expected that if the license is known for the package, it would also be known for the versions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions