Skip to content

Create Allowlist for datasource ecosystems (and aliases?) #5285

@michaelkedar

Description

@michaelkedar

We currently place a lot of trust in our data sources to not publish bad data outside of their jurisdiction.
Nearly all data sources should only actually publish for 1 or 2 ecosystems.

We should add a list of expected ecosystems to our SourceRepository / source.yaml and filter out affected[] for things that do not match when we ingest.
GHSA & Malicious Packages would need an exception, since we trust them to publish for most ecosystems anyway.

Similarly, we might want to restrict alias computation for some ecosystems that may be misusing the aliases field and causing unnecessary linkages between records.

Metadata

Metadata

Assignees

No one assigned

    Labels

    data qualityIssues with data qualityneeds-gcp-infra-accessTo be able to adequately work on this issue will require access to GCP infrastructureworkerWorker-related infrastructure

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions