Skip to content

tail: Dependabot does not re-evaluate fixed uv.lock alerts #769

Closed

Description

@zaebee

Three alerts stay open on dependencies that main already carries at a patched version, while GitHub's dependency graph reports exactly those patched versions.

Evidence (2026-10-31)

Alert Package Vulnerable Lock version GitHub graph version Created Updated
#46 opentelemetry-api <= 1.45.0 1.45.1 1.45.1 2026-10-22 22:35 2026-10-22 22:35
#47 virtualenv >= 21.14.9, < 21.14.13 21.15.2 21.15.2 2026-10-30 17:46 2026-10-30 17:46
#48 virtualenv >= 21.14.8, < 21.14.10 21.15.2 21.15.2 2026-10-31 06:49 2026-10-31 06:49
#49 happy-dom (ui/) >= 17.0.0, <= 21.0.3 21.0.4 n/a (ui manifest) 2026-10-31 11:17 2026-10-31 11:17

Every alert has updated_at == created_at and fixed_at: null — no scan has touched them since creation.

What was checked and ruled out

Next step

Re-check after the next scheduled Dependabot scan (alerts normally re-evaluate on push to the default branch and on a schedule). If the three are still open and still report updated_at == created_at:

  1. Open a GitHub Support ticket under Security/Dependabot with the alert numbers, the advisory IDs, and the GraphQL evidence above — the alert state is inconsistent with the dependency graph GitHub itself reports.
  2. Do not dismiss them as "inaccurate": the vulnerabilities were real, the fix is real, and a dismissal would hide whether the re-evaluation works.
  3. If the same staleness hits a future alert, the alarm is: alerts lag behind the dependency graph, so a green "0 open" cannot be trusted as proof that a bump worked.

Recheck command

gh api 'repos/zaebee/codegraph-brain/dependabot/alerts?state=open&per_page=50' \
  --jq '.[] | "#\(.number) \(.dependency.package.name) \(.security_vulnerability.vulnerable_version_range) updated=\(.updated_at) fixed=\(.fixed_at // "-")"'

Close this tail once /security/dependabot shows zero alerts or all three at state: fixed.

Activity

  1. added
    tailLoose end: something left to check or finish later
    on Oct 31, 2026
  2. zaebee commented on Oct 31, 2026

    @zaebee
    OwnerAuthor

    Another alert appeared while this tail is open: #50 filelock (GHSA-v4x8-3wr5-3wq8, high) — created 2026-10-31 11:43, fixed by #770 (filelock 3.29.1 -> 4.2.5).

    Same pattern: the new alert is created promptly, while the already-fixed ones (#46/#47/#48/#49) keep updated_at == created_at and stay open. That strengthens the re-evaluation hypothesis: alert creation works, alert closing does not happen on dependency-graph changes.

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

    tailLoose end: something left to check or finish later

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions