You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No files changed β the vulnerabilities were already resolved by package updates in the main branch prior to this issue being assigned.
Notes
This is a resolved-by-upstream-fix scenario. The fleet monitor issue was filed on 2026-05-19 when the package-lock.json contained vulnerable transitive dependencies. Those packages are no longer present in the dependency tree as of the current main branch. The dependency-audit.yml workflow has been passing continuously since 2026-06-01. No further action is required beyond closing this issue.
Confirm dependency-audit.yml workflow running successfully in CI
Tests to Write
None β this is a resolved-by-upstream-fix scenario. No code changes required.
Test Command
npm test (unit tests), npm run check (lint/format), npm audit (vulnerability audit)
Exception (Phase 2/3)
Skipping TDD and implementation phases per the exception rule: this is a pure configuration/dependency issue with no observable behavioral change to implement β the vulnerability was fixed upstream in the npm dependency graph.
Confirmed dependency-audit.yml workflow has been passing continuously since 2026-06-01
Root Cause
The workflow was operating correctly β it failed because it detected genuine npm vulnerabilities:
brace-expansion 5.0.2β5.0.5 (moderate) β GHSA-jxxr-4gwj-5jf2: DoS via large numeric range
fast-uri β€3.1.1 (high) β GHSA-v39h-62p7-jpjc: host confusion via percent-encoded authority
These were transitive dependencies now absent from the current dependency tree. Additionally, the workflow was updated from @v1 β @v2 of the reusable workflow in June 2026.
Test Results
Test Suites: 12 passed, 12 total
Tests: 301 passed, 301 total
npm audit: 0 vulnerabilities
npm run check: 0 errors
dev-lead-lint: pass (pre-existing warnings only)
Files Changed
No files changed β the vulnerabilities were resolved upstream; the dependency-audit.yml caller stub is already on @v2 and correct.
Notes
This is a resolved-by-upstream-fix scenario. The fleet monitor issue was filed on 2026-05-19 when the package-lock.json contained vulnerable transitive dependencies. Those packages are no longer present in the dependency tree. All 50 recent workflow runs show success. No further action required.
β Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-05-19 (57 days) β the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.
Activity
don-petry commentedon Jun 8, 2026
Dev-Lead Implementation Plan
Issue: #304 β [Fleet Monitor] petry-projects/google-app-scripts β dependency-audit.yml
Root Cause Investigation
After investigating the 100% failure rate (40/40 runs), I found the following:
Root cause:
npm audit --audit-level=lowwas detecting two real vulnerabilities in thepackage-lock.jsonat the time of the May 19, 2026 fleet report:maxDoS protectionThe workflow was behaving correctly β it detected genuine vulnerabilities and failed the build.
Current State
npm auditnow reports 0 vulnerabilities (both packages are no longer transitive dependencies in the current lockfile)dependency-audit.ymlwas also updated from@v1β@v2of the reusable workflow as part of org-wide changes merged June 7, 2026Scope
No code changes are required β the issue is already resolved. This plan documents the investigation and verification steps.
Implementation Checklist
npm auditnow reports 0 vulnerabilitiesnpm test)npm run check)dependency-audit.ymlruns succeed in CI (most recent 50 runs all pass)Tests to Write
No new tests required β this was a dependency vulnerability issue, not a logic defect. The
dependency-audit.ymlworkflow itself is the test.Test Command
npm test(all 301 unit tests),npm run check(lint/format),npm audit(0 vulnerabilities)don-petry commentedon Jun 8, 2026
Dev-Lead: Implementation Complete
Plan Execution
npm auditnow reports 0 vulnerabilities (fixed upstream by package updates)Root Cause
The workflow was failing correctly β it detected two genuine npm vulnerabilities:
These were transitive dependencies. Both have since been resolved: neither package appears in the current dependency tree.
Test Results
Files Changed
No files changed β the vulnerabilities were already resolved by package updates in the main branch prior to this issue being assigned.
Notes
This is a resolved-by-upstream-fix scenario. The fleet monitor issue was filed on 2026-05-19 when the
package-lock.jsoncontained vulnerable transitive dependencies. Those packages are no longer present in the dependency tree as of the current main branch. Thedependency-audit.ymlworkflow has been passing continuously since 2026-06-01. No further action is required beyond closing this issue.don-petry commentedon Jun 9, 2026
Dev-Lead Implementation Plan
Issue: #304 β [Fleet Monitor] petry-projects/google-app-scripts β dependency-audit.yml
Scope
Investigate and resolve the 100% failure rate (40/40 runs) for the
dependency-audit.ymlworkflow that was reported on 2026-05-19.Investigation Findings
This issue was previously investigated (see prior comments). After verifying the current state:
npm audit --audit-level=lowcorrectly detected two real vulnerabilities in thepackage-lock.jsonas of May 2026:npm auditreports 0 vulnerabilities; all workflow runs since June 1, 2026 are passingImplementation Checklist
npm auditreports 0 vulnerabilitiesnpm testβ 301/301)npm run checkβ 0 errors)dependency-audit.ymlworkflow running successfully in CITests to Write
None β this is a resolved-by-upstream-fix scenario. No code changes required.
Test Command
npm test(unit tests),npm run check(lint/format),npm audit(vulnerability audit)Exception (Phase 2/3)
Skipping TDD and implementation phases per the exception rule: this is a pure configuration/dependency issue with no observable behavioral change to implement β the vulnerability was fixed upstream in the npm dependency graph.
don-petry commentedon Jun 9, 2026
Dev-Lead: Implementation Complete
Plan Execution
npm auditreports 0 vulnerabilities (confirmed:found 0 vulnerabilities)dependency-audit.ymlworkflow has been passing continuously since 2026-06-01Root Cause
The workflow was operating correctly β it failed because it detected genuine npm vulnerabilities:
These were transitive dependencies now absent from the current dependency tree. Additionally, the workflow was updated from
@v1β@v2of the reusable workflow in June 2026.Test Results
Files Changed
No files changed β the vulnerabilities were resolved upstream; the
dependency-audit.ymlcaller stub is already on@v2and correct.Notes
This is a resolved-by-upstream-fix scenario. The fleet monitor issue was filed on 2026-05-19 when the
package-lock.jsoncontained vulnerable transitive dependencies. Those packages are no longer present in the dependency tree. All 50 recent workflow runs show success. No further action required.don-petry commentedon Jul 15, 2026
β Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-05-19 (57 days) β the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.