Skip to content

build(deps): bump the npm-security group across 1 directory with 6 updates - #217

Merged
ooloth merged 2 commits into
mainfrom
dependabot/npm_and_yarn/npm-security-43b7d942db
Nov 6, 2026
Merged

ooloth merged 2 commits into
mainfrom
dependabot/npm_and_yarn/npm-security-43b7d942db

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 6, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-security group with 6 updates in the / directory:

Package From To
happy-dom 20.14.6 21.0.4
satori 0.18.3 0.33.5
sharp 0.34.5 0.35.5
tmp 0.0.33 removed
ws 7.5.10 8.22.1
uuid 8.3.2 14.0.3

Updates happy-dom from 20.14.6 to 21.0.4

Release notes

Sourced from happy-dom's releases.

v21.0.4

👷‍♂️ Patch fixes

  • Fixed a code injection vulnerability in the ESM compiler - By @​capricorn86
  • Fixed cross-origin isolation so opaque-origin data: iframes cannot access their parent or top window - By @​capricorn86

v21.0.3

👷‍♂️ Patch fixes

  • Fixes security vulnerability where authorization header was forwarded when redirecting - By @​capricorn86

v21.0.2

👷‍♂️ Patch fixes

v21.0.1

👷‍♂️ Patch fixes

v21.0.0

💣 Breaking Changes

  • Disables CSS and IFrame loading by default to prevent server-side request forgery (SSRF) - By @​capricorn86
    • An attacker could embed <iframe> or <link rel="stylesheet"> elements in untrusted HTML to make Happy DOM send HTTP requests from the server to attacker-chosen URLs, including internal services. This could allow access to otherwise unreachable endpoints or trigger unintended actions, depending on the application and its network access.
    • The settings property disableCSSFileLoading has been deprecated
    • Added the new settings properties enableCSSFileLoading and enableIframePageLoading
    • If you don't believe that you are at risk, you can keep the same behavior as in <=v20.14.6 by sending in { enableCSSFileLoading: true, enableIframePageLoading: true } as broswer settings (e.g. new Window({ settings }));
Commits
  • fd16352 fix: Fixed a code injection vulnerability in the ESM compiler (#2537)
  • 75ab0fb fix: Fixed cross-origin isolation so opaque-origin data: iframes cannot acces...
  • 875ef5c fix: Fixes security vulnerability where authorization header was forwarded wh...
  • 1f3ffdf fix: Fixes SSRF security vulnerability by doing a target-origin bypass in the...
  • f55c7e0 chore: Update security documentation (#2509)
  • 2b91e68 fix: Adds alias for enabling CSS and iframe loading in server-renderer (#2503)
  • 0a99c75 BREAKING CHANGE: Disables CSS and IFrame loading by default (#2502)
  • See full diff in compare view

Updates satori from 0.18.3 to 0.33.5

Release notes

Sourced from satori's releases.

0.33.5

0.33.5 (2026-09-22)

Bug Fixes

0.33.4

0.33.4 (2026-08-24)

Bug Fixes

0.33.3

0.33.3 (2026-08-21)

Bug Fixes

0.33.2

0.33.2 (2026-08-21)

Bug Fixes

0.33.1

0.33.1 (2026-08-21)

Bug Fixes

  • Improve cache and update benchmark (~12% faster) (#787) (ed7d78e)

0.33.0

0.33.0 (2026-08-20)

Features

0.32.0

0.32.0 (2026-08-20)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for satori since your current version.

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.


Updates sharp from 0.34.5 to 0.35.5

Release notes

Sourced from sharp's releases.

v0.35.5

https://github.com/lovell/sharp-libvips/releases/tag/v1.3.4

  • Add upper bounds check on length of linear and GIF delay arrays.

  • Improve error handing when WebAssembly fallback also fails. #4593 @​lazerg

  • TypeScript: Allow multi-frame options for JXL output. #4602 @​ramin-010

  • TypeScript: Remove non-existent named export. #4604

  • Increase accepted dimensions when extending an image. #4605

  • Improve gain map support for extract and rotate operations. #4606

  • Tests: Ensure composite tests pass on big endian platforms. #4609

v0.35.5-rc.1

https://github.com/lovell/sharp-libvips/releases/tag/v1.3.4-rc.1

  • Add upper bounds check on length of linear and GIF delay arrays.

  • Improve error handing when WebAssembly fallback also fails. #4593 @​lazerg

  • TypeScript: Allow multi-frame options for JXL output. #4602 @​ramin-010

  • TypeScript: Remove non-existent named export. #4604

  • Increase accepted dimensions when extending an image. #4605

  • Improve gain map support for extract operation. #4606

... (truncated)

Commits
  • 51a990f Release v0.35.5
  • 96de105 Upgrade to sharp-libvips v1.3.4
  • 3a61390 CI: Configure Dependabot with all package.json locations
  • 4940c50 Improve gain map support for rotate/flip/flop ops
  • 20654aa Prerelease v0.35.5-rc.1
  • ef4f934 CI: Upgrade to Ubuntu 26.04
  • 358df95 Upgrade to libvips v8.18.7
  • 49f4903 Improve gain map support for rotate-then-extract #4606
  • 0e2e55e Silence a couple of compiler/static analysis warnings
  • cef3b8c Improve gain map support for extract operation #4606
  • Additional commits viewable in compare view

Removes tmp

Updates ws from 7.5.10 to 8.22.1

Release notes

Sourced from ws's releases.

8.22.1

Bug fixes

  • The path of IPC URLs is no longer truncated at : (#2344).

Other notable changes

8.22.0

Features

  • Introduced the protocols option (8b918b01).

Bug fixes

  • Calling websocket.close() with invalid arguments no longer transitions the state to WebSocket.CLOSING (#2337).

8.21.3

Bug fixes

  • The server now correctly rejects permessage-deflate offers if the incoming client_max_window_bits parameter value is smaller than its configured clientMaxWindowBits (e97a20ea).

8.21.2

Bug fixes

  • Fixed a test for CITGM (2eb3be0b).

8.21.1

Bug fixes

  • Empty fragments are now counted toward the limit (a2f4e7c0).
  • The default values of the maxBufferedChunks and maxFragments options have been reduced (f197ac65).

8.21.0

Features

... (truncated)

Commits
  • c18a80a [dist] 8.22.1
  • 2ab3d3e [minor] Use http.websocket{M,Unm}ask() if possible (#2347)
  • c9efa88 [ci] Test on node 27
  • aa91518 [test] Skip test on Node.js versions where it does not apply (#2340)
  • b54ca10 [fix] Do not truncate the URL path of IPC URLs at : (#2344)
  • 85319a7 [minor] Prevent Sender.frame() from returning empty chunks
  • 297202c [dist] 8.22.0
  • 8b918b0 [feature] Introduce the protocols option
  • 73e03eb [ci] Update actions/setup-node action to v7
  • d9b8954 [fix] Change the ready state after validating the arguments (#2337)
  • Additional commits viewable in compare view

Updates uuid from 8.3.2 to 14.0.3

Release notes

Sourced from uuid's releases.

v14.0.3

14.0.3 (2026-10-09)

Bug Fixes

v14.0.2

14.0.2 (2026-08-18)

Bug Fixes

  • v1: carry nsecs overflow into the timestamp's high bits (#972) (6adcc1d)
  • v1: set the multicast bit on v1Bytes's own randomly-generated node (#973) (b1da338)
  • v7: align default seq formula in v7Bytes with updateV7State (#965) (a67db57)

v14.0.1

14.0.1 (2026-06-20)

Bug Fixes

  • add types condition to node export for moduleResolution bundler (#961) (27ffae5)

v14.0.0

14.0.0 (2026-04-19)

⚠ BREAKING CHANGES

  • expect crypto to be global everywhere (requires node@20+) (#935)
  • drop node@18 support (#934)

Features

Bug Fixes

  • expect crypto to be global everywhere (requires node@20+) (#935) (f2c235f)
  • Use GITHUB_TOKEN for release-please and enable npm provenance (#925) (ffa3138)

v13.0.2

13.0.2 (2026-05-04)

Bug Fixes

... (truncated)

Changelog

Sourced from uuid's changelog.

14.0.3 (2026-10-09)

Bug Fixes

14.0.2 (2026-08-18)

Bug Fixes

  • v1: carry nsecs overflow into the timestamp's high bits (#972) (6adcc1d)
  • v1: set the multicast bit on v1Bytes's own randomly-generated node (#973) (b1da338)
  • v7: align default seq formula in v7Bytes with updateV7State (#965) (a67db57)

14.0.1 (2026-06-20)

Bug Fixes

  • add types condition to node export for moduleResolution bundler (#961) (27ffae5)

14.0.0 (2026-04-19)

Security

  • Fixes GHSA-w5hq-g745-h8pq: v3(), v5(), and v6() did not validate that writes would remain within the bounds of a caller-supplied buffer, allowing out-of-bounds writes when an invalid offset was provided. A RangeError is now thrown if offset < 0 or offset + 16 > buf.length.

⚠ BREAKING CHANGES

  • crypto is now expected to be globally defined (requires node@20+) (#935)
  • drop node@18 support (#934)
  • upgrade minimum supported TypeScript version to 5.4.3, in keeping with the project's policy of supporting TypeScript versions released within the last two years

13.0.0 (2025-09-08)

⚠ BREAKING CHANGES

  • make browser exports the default (#901)

Bug Fixes

12.0.0 (2025-09-05)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for uuid since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

…dates

Bumps the npm-security group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [happy-dom](https://github.com/capricorn86/happy-dom) | `20.14.6` | `21.0.4` |
| [satori](https://github.com/vercel/satori) | `0.18.3` | `0.33.5` |
| [sharp](https://github.com/lovell/sharp) | `0.34.5` | `0.35.5` |
| [tmp](https://github.com/raszi/node-tmp) | `0.0.33` | `removed` |
| [ws](https://github.com/websockets/ws) | `7.5.10` | `8.22.1` |
| [uuid](https://github.com/uuidjs/uuid) | `8.3.2` | `14.0.3` |



Updates `happy-dom` from 20.14.6 to 21.0.4
- [Release notes](https://github.com/capricorn86/happy-dom/releases)
- [Commits](capricorn86/happy-dom@v20.14.6...v21.0.4)

Updates `satori` from 0.18.3 to 0.33.5
- [Release notes](https://github.com/vercel/satori/releases)
- [Commits](vercel/satori@0.18.3...0.33.5)

Updates `sharp` from 0.34.5 to 0.35.5
- [Release notes](https://github.com/lovell/sharp/releases)
- [Commits](lovell/sharp@v0.34.5...v0.35.5)

Removes `tmp`

Updates `ws` from 7.5.10 to 8.22.1
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](websockets/ws@7.5.10...8.22.1)

Updates `uuid` from 8.3.2 to 14.0.3
- [Release notes](https://github.com/uuidjs/uuid/releases)
- [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md)
- [Commits](uuidjs/uuid@v8.3.2...v14.0.3)

---
updated-dependencies:
- dependency-name: happy-dom
  dependency-version: 21.0.4
  dependency-type: direct:development
  dependency-group: npm-security
- dependency-name: satori
  dependency-version: 0.33.5
  dependency-type: direct:development
  dependency-group: npm-security
- dependency-name: sharp
  dependency-version: 0.35.5
  dependency-type: direct:development
  dependency-group: npm-security
- dependency-name: tmp
  dependency-version:
  dependency-type: indirect
  dependency-group: npm-security
- dependency-name: ws
  dependency-version: 8.22.1
  dependency-type: indirect
  dependency-group: npm-security
- dependency-name: uuid
  dependency-version: 14.0.3
  dependency-type: indirect
  dependency-group: npm-security
...

Signed-off-by: dependabot[bot] <support@github.com>
#217

Dependabot's lockfile for the security bumps failed `npm ci` under
npm 11.6.2, the npm bundled with the Node 25.1.0 that CI reads from
.nvmrc. npm reported the lockfile out of sync with package.json
("Missing: agent-base@9.0.0 from lock file" and the rest of the
proxy-agent 9.x tree), so Format, Lint, Tests and Types all failed at
install. npm 12 accepts the same file, which suggests Dependabot
resolved it with a newer npm than CI runs.

The lockfile is now regenerated from main's, with this PR's
package.json, using npm 11.6.2 and --before=2026-11-03. The date cap
keeps the newest adopted release at @lhci/cli 0.16.0 (2026-11-02),
so nothing published in the last few days enters the tree:
@sentry/node resolves to 11.10.0 rather than 11.11.0 and
lighthouse's chrome-launcher to 1.2.2 rather than 1.2.3. Every
security fix the PR targets is still in place.

The cost is that @sentry/bundler-plugins 11.10.0 pulls glob 13.0.6
and minimatch 10.2.6, which carry moderate advisories. Both sit in
the dev-only Lighthouse tree and never see untrusted patterns.

npm ci (npm 11.6.2), tsc, vitest (875 tests), eslint and prettier
all pass with the new lockfile.

@ooloth ooloth left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving at 9e32f49. Dependabot's lockfile failed npm ci under the npm 11.6.2 that CI uses, so 9e32f49 regenerates it with that npm, capped at releases from before 2026-11-03.

The hand-started Check run passed Build, Metadata and Lighthouse at this head. The npm version mismatch is tracked in #218.

@ooloth
ooloth merged commit da49dae into main Nov 6, 2026
27 checks passed
@ooloth
ooloth deleted the dependabot/npm_and_yarn/npm-security-43b7d942db branch November 6, 2026 06:02
@ooloth

ooloth commented Nov 6, 2026

Copy link
Copy Markdown
Owner

Verified in production: #217 is serving and every part of the claim holds.

PR #217, merged as da49dae on 2026-11-06 at 06:02 UTC. No ticket. The claim comes from the PR itself: the security-update bumps land on main, and the site still builds, deploys and serves.

Rollout

  • The Check run on da49dae passed Types, Formatting, Linting, Tests, Build, Metadata, Lighthouse and Deploy.
  • wrangler pages deployment list --project-name=michaeluloth --environment=production shows the newest production deployment, 1771157c, with source da49dae. Before the merge, production was ee89221d, built from 73fed3a.
  • https://michaeluloth.com/ returns the same bytes as https://1771157c.michaeluloth.pages.dev/ (SHA-256 b4cfe9c1b2c5… for both), so the custom domain serves the new deployment.

Verdicts

  • The bumps are on main: proven. package-lock.json at 73fed3a → da49dae: happy-dom 20.14.6 → 21.0.4, satori 0.18.3 → 0.33.5, sharp 0.34.5 → 0.35.5, ws 7.5.10 → 8.22.1, uuid 8.3.2 → 14.0.3, @lhci/cli 0.15.1 → 0.16.0, lighthouse 12.6.1 → 13.6.0. tmp 0.1.0 and extract-zip 2.0.1 are no longer in the tree.
  • The site builds and deploys with them: proven. Build, Metadata, Lighthouse and Deploy all succeeded on da49dae, which produced deployment 1771157c.
  • Home, /blog/, /rss.xml and a post serve: proven. All four return 200 on michaeluloth.com. The post checked was /alexis-king-constructive-data-modeling/, the newest item in the feed.
  • They render: proven. Full-page screenshots in headless Chrome show the home page with its photo and its featured and recent writing, /blog/ listing posts from Sep 14, 2026 back to 2019, the post with its blockquotes and "Older" link, and the feed as XML whose first item is "What is a type system for?".
  • Nothing else changed: proven. Each page is the same size before and after. The post page differs from the old deployment only in Next's 21-byte build ID (IsvOfUy9m-Gp8ruCJleJ6 → wSXIzKAS2L1PPX2C79_im), and the feed only in lastBuildDate (05:03:23 → 06:05:37 GMT), with 38 items both times. The home and /blog/ pages also start differing at the build ID; I didn't diff the rest of them byte by byte.

Not observable here

  • Console errors. Headless Chrome logged no console or network errors, but that capture may not emit console messages at all, so it is no evidence either way. Checking would need Playwright or the browser's own devtools.
  • Runtime effect of the bumps. The bumped packages are dev dependencies used by tests, Lighthouse and the hand-run OG image script, so the served pages don't contain them.

ooloth added a commit to ooloth/dotfiles that referenced this pull request Nov 6, 2026
The dependency bump check compared releases, the tree and advisories,
but never tried to install the lockfile. On ooloth/michaeluloth.com#217
Dependabot wrote a lockfile that npm 12 accepts and npm 11.6.2, the npm
CI gets from the repo's .nvmrc Node, rejects as out of sync. The script
reported nothing about it; only reading CI's failed checks caught it.

Each npm lockfile now gets an Install section. The script takes the npm
version from package.json's packageManager, or else from the nearest
.nvmrc or .node-version, mapping that Node version (exact, or a major
or major.minor prefix that skips prereleases) to its bundled npm through
nodejs.org's release index. It then runs `npm ci --dry-run
--ignore-scripts` under that npm with `npm exec`, in the temp copy of
the head that npm ls and npm audit already use, so nothing is installed
and no package script runs. An EUSAGE rejection is flagged with npm's
Missing/Invalid lines, and acceptance is reported with the npm version
and where it came from.

When the repo declares no version the script can resolve, such as an
lts/* alias, that is flagged and the check runs with the local npm so a
rejection still shows. A manifest with workspaces is flagged for a check
by hand, since npm ci needs every member's package.json. Any other npm
failure, or an unreachable or malformed index, exits 2. curl moves to
the shared helpers section, since the npm side now uses it too.

Run against #217 the check accepts the merged lockfile under npm 11.6.2
from .nvmrc, and it rejects Dependabot's original lockfile with
"Missing: agent-base@9.0.0 from lock file" under the same npm.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant