[auto-sec] aspire.dev: remediate 12 frontend npm security alerts - #1645
[auto-sec] aspire.dev: remediate 12 frontend npm security alerts#1645David Pine (IEvangelist) wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
🔵 Needs a closer look
Dependency/security remediations with a regenerated lockfile require CI confirmation to ensure the updated resolution graph doesn’t introduce build/runtime regressions.
Pull request overview
This PR remediates a cluster of frontend npm Dependabot security alerts for aspire.dev by updating a few direct dependencies and pinning vulnerable transitives via pnpm overrides, with a regenerated lockfile to reflect the resolved versions.
Changes:
- Bump direct frontend deps:
astro,sharp, andvitest. - Add/refresh
pnpm-workspace.yamloverridesto force patched transitive versions (@vitest/mocker,fflate,js-yaml,nanoid,smol-toml,svgo). - Regenerate
pnpm-lock.yamlto capture the new resolution graph.
File summaries
| File | Description |
|---|---|
| src/frontend/pnpm-workspace.yaml | Adds/updates pnpm overrides to pin vulnerable transitives to patched versions. |
| src/frontend/package.json | Bumps direct dependencies (astro, sharp, vitest) involved in the security remediation. |
| src/frontend/pnpm-lock.yaml | Updated dependency resolution output consistent with the new direct deps + overrides. |
Review details
- Files reviewed: 2/3 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "@mdx-js/mdx": "^3.1.1", | ||
| "asciinema-player": "^3.17.0", | ||
| "astro": "^7.1.3", | ||
| "astro": "^7.2.8", |
Clears all open Dependabot alerts for src/frontend (1 critical, 6 high, 5 medium): - astro 7.1.3 -> 7.2.10 (critical GHSA + medium) - sharp 0.35.3 -> 0.35.4 (high) - vitest 4.1.10 -> 4.1.11; @vitest/mocker -> 4.1.11 (medium) - pnpm overrides: js-yaml 4.3.2, nanoid 3.3.18, svgo 4.1.0, fflate 0.7.5, smol-toml 1.7.1 Verified: pnpm install OK; pnpm audit -> no known vulnerabilities; astro sync OK. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
76b7dda to
16f96b2
Compare
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
Alistair Matthews (alistairmatthews)
left a comment
There was a problem hiding this comment.
This all works on my machine. Approved.
[auto-sec]Canonical — aspire.dev frontend npm security clusterCanonical remediation PR for the aspire.dev dependency/security cluster.
Branch
dapire/security-deps/aspire.dev-frontend-npm, based on the latestorigin/main, labeledautomated-security.Alerts addressed — all 12 open Dependabot alerts (1 critical, 6 high, 5 moderate)
7.1.3 → 7.2.100.35.3 → 0.35.44.3.23.3.181.7.14.1.00.7.54.1.10 → 4.1.114.1.11How
src/frontend/package.json:astro,sharp,vitest.src/frontend/pnpm-workspace.yamloverrides— therepo's existing security-remediation mechanism. Stale overrides refreshed
(
js-yaml4.3.1→4.3.2,nanoid3.3.17→3.3.18,svgo=4.0.0→<4.1.0:4.1.0)and new surgical range overrides added (
fflate,smol-toml,@vitest/mocker).src/frontend/pnpm-lock.yamlregenerated withpnpm install(astro minor bumpaccounts for the large lockfile delta).
Verification
pnpm install— succeeds; lockfilenpm ci-consistent.pnpm audit— No known vulnerabilities found.pnpm exec astro sync— config + all integrations + content types load under astro7.2.10.Supersedes (Dependabot PRs folded into this canonical cluster)
These remain open and tracked until this canonical PR is confirmed green, per the
closure gate; they will then be closed as superseded.
canonical_count_frontend-npm = 1