Repository navigation
Closed
Labels
tailLoose end: something left to check or finish laterLoose end: something left to check or finish later
Description
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
- Dependency graph is current, not stale. GraphQL
dependencyGraphManifestslistsuv.lockwithparseable: trueandvirtualenv -> = 21.15.2,opentelemetry-api -> = 1.45.1. So GitHub's parser reads the lock and sees the fixed versions; this is not auv.lockparsing failure. - Dependabot alerts are enabled (
GET /repos/zaebee/codegraph-brain/vulnerability-alerts→ 204). - Dependabot security updates are enabled (
security_and_analysis.dependabot_security_updates.status = enabled). - GitHub status is operational (Actions; no Dependabot incident at the time).
- The fixes themselves are in
main: fix(deps): bump virtualenv past the two open Dependabot alerts #761 (virtualenv 21.14.9 → 21.15.2), build(deps): bump opentelemetry-api from 1.39.1 to 1.45.1 in the uv group across 1 directory #754 (opentelemetry-api 1.39.1 → 1.45.1), fix(deps): bump happy-dom past the high-severity advisory #766 (happy-dom 20.10.2 → 21.0.4). - The graph change itself should be a scan trigger:
mainreceived squash commits after the bumps (21d707d,a87e0c3,d50b4ec,764bd00,aba2814,b9f6464,1c7a771).
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:
- 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.
- Do not dismiss them as "inaccurate": the vulnerabilities were real, the fix is real, and a dismissal would hide whether the re-evaluation works.
- 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.
Metadata
Metadata
Assignees
Labels
tailLoose end: something left to check or finish laterLoose end: something left to check or finish later
Activity
zaebee commentedon Oct 31, 2026
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_atand stayopen. That strengthens the re-evaluation hypothesis: alert creation works, alert closing does not happen on dependency-graph changes.