Skip to content

Include Maintainers and FundingLinks in core.Package #34

@andrew

Description

@andrew

enrichment now exposes FundingLinks and Maintainers on PackageInfo (git-pkgs/enrichment#26), but only the ecosyste.ms backend can populate them. The direct-registry backend gets nothing because core.Package carries neither field.

Maintainers already exist here as core.Maintainer with a per-registry FetchMaintainers(ctx, name) call. That works for single lookups but BulkFetchPackages callers would need N extra requests to fill them in. Funding has no support at all.

Proposed:

  • Add Maintainers []Maintainer to core.Package and populate it in FetchPackage for registries where the package endpoint already returns maintainer data (npm, hex, rubygems, cargo owners, etc.). Registries that need a separate call can keep returning nil here and rely on FetchMaintainers.
  • Add FundingLinks []string to core.Package and populate from registries that expose it: npm funding, rubygems funding_uri, hex links.Sponsor, cargo (via repo metadata), pypi project_urls Funding/Sponsor entries.

Once that lands, enrichment.RegistriesClient.BulkLookup can copy both fields straight through and the hybrid client will have parity with ecosyste.ms for packages routed to direct registries.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions