Skip to content

Advisory versioning to avoid duplication and track changes #1793

Description

@keshav-space

ATM whenever import pipeline encounters an advisory with modified content, it treats it as a new advisory. This makes it harder to track changes in advisories over time. Instead of treating modified advisories as new ones, we should start versioning the advisory. To do this we can use aliases like CVE, GHSA, PySec. Whenever pipeline receives a modified content for given alias, it should store the modified content as a new version of the existing advisory (imported from the same pipeline).

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions