ungoogled-software/ungoogled-chromium

Spoof WebGPU info

Open

#3,670 opened on Feb 25, 2026

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Python (771 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (18,674 stars)
PR merge metrics
 (Avg merge 3d) (8 merged PRs in 30d)

Description

Description

The current "Spoof Webgl Info" option but for WebGPU.

Who's implementing?

  • I'm willing to implement this feature myself

The problem

Ungoogled Chromium has a patch which adds a "Spoof Webgl Info" option which replaces the UNMASKED RENDERER/VENDOR of WebGL with the string " " (an empty space). However, it is possible to get similar hardware information using the WebGPU API: await navigator.gpu.requestAdapter()

Possible solutions

Either integrate it into the existing option (since the intent is the same: hiding hardware information) or add a new option which redacts the vendor/device information like WebGL.

Alternatives

Adding an option to disable WebGPU entirely (like what we have with WebGL).

Extensions are not alternatives; they cannot inject code into web workers.

Additional context

No response

Contributor guide

Research direction
Examine the existing 'Spoof WebGL Info' patch in Ungoogled Chromium to understand its implementation, then replicate the approach for WebGPU by overriding the vendor and device information returned by navigator.gpu.requestAdapter().
Tech stack
javascript
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitUnderstanding of browser patching
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40