Skip to content

Advisories deleted from source Git repository not being marked as withdrawn #2101

Open

Description

@andrewpollock

Describe the bug
Whilst doing some validation analysis for bitnami/vulndb#336 I noticed that records now showing as deleted are not marked as withdrawn in OSV.dev

Then I remembered #829 removed this behaviour due to some sort of blip at the time in the GitHub Advisory Database, whereas a safer approach would be to do a threshold-based operation like what's being done for GCS in #2030

Expected behaviour
I was of the expectation that deleted records were marked as withdrawn and that Git-based source imports would catch up to the commits deleting a record

Additional context

Activity

  1. github-actions commented on Jul 18, 2024

    @github-actions

    This issue has not had any activity for 60 days and will be automatically closed in two weeks

  2. added
    staleThe issue or PR is stale and pending automated closure
    on Jul 18, 2024
  3. removed
    staleThe issue or PR is stale and pending automated closure
    on Jul 29, 2024
  4. removed their assignment
    on Apr 2, 2025
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

    backlogImportant but currently unprioritizeddata qualityIssues with data quality

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions