Skip to content

Autopilot: clear high-severity js-yaml alert (2026-09-11) - #34

Open
ivanagas wants to merge 1 commit into
masterfrom
autopilot/2026-09-11
Open

Autopilot: clear high-severity js-yaml alert (2026-09-11)#34
ivanagas wants to merge 1 commit into
masterfrom
autopilot/2026-09-11

Conversation

@ivanagas

Copy link
Copy Markdown
Owner

Dependencies

npm audit fix (no --force) — 11 advisories → 9. Lockfile only, no package.json change.

Advisory Severity Package Action
GHSA js-yaml prototype pollution high js-yaml resolved transitively, 4.1.0 chain
colord moderate colord resolved transitively

Deferred — the two open Dependabot alerts, both Vue 2 EOL:

Alert Severity Package Why deferred
#68 low vue first patched version is 3.0.0-alpha.0 — a Vue 2 → 3 migration
#52 medium vue-template-compiler no patched version exists; it only ships for Vue 2

The 9 remaining npm audit findings are the same story — @vue/cli-service, @vue/cli-plugin-*, bootstrap-vue, portal-vue. Every fix npm audit offers for them is isSemVerMajor: true, and the "fix" it suggests (@vue/cli-plugin-babel@3.12.1) is a downgrade from the installed 5.x. Not worth taking on a static site to clear a low.

Clearing these properly means migrating off Vue 2, which is end-of-life. That's a project, not a dependency bump — flagged in the run report rather than attempted here.

Errors

None. The project has 43 $exception events all time, the most recent from 2026-06-01 — nothing in the last 90 days.

Verification

npm run buildpassed (Vue CLI, dist/ written, 2.4s).
Netlify deploy preview on this PR is the real check — clean install against the changed lockfile.

Nothing to click after deploy: this is a lockfile-only change with no runtime dependency moved.

npm audit fix, no --force: js-yaml 4.1.0 chain and colord resolved.
Remaining 9 advisories are all the Vue 2 EOL toolchain and need a major
upgrade, so they are deferred rather than forced.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant