Skip to content

Store latest non vulnerable version and next vulnerable version for a package in DB #1416

Description

@TG1999

Currently, we are computing the non-vuln and next-vuln versions every time we call the API, instead, we should store them and use an improver to keep the data current.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions