Signals · system · counted, not scored by the rubric
Plugins
The number of entries in navigator.plugins and a hash of their names.
Rubric 1.0.0 does not print a prior for this value. The population still compares it, so the box beside this text counts how many of the devices these sites have read share yours.
How a page reads it
Modern browsers no longer load plugins, but they still report a fixed list: Chrome reports five PDF viewer entries. The collector records the count and the hash.
Why it splits browsers apart
Almost every current desktop browser reports the standard list, so the common value is the fixed list. An empty list, which headless and automated browsers often report, is a small group.
What moves it
Disabling the built-in PDF viewer, or running a browser build or mode that reports none.
What moving it costs
An empty plugin list in a browser that claims to be desktop Chrome is one of the oldest automation signals there is.
How the count is made
Your value is compared with the latest reading of every device the eight sites read in the last 365 days, this browser's own rows left out. The share is (devices sharing it + 1) ÷ (population + 1), and the bits are −log₂ of that. Why the counts sit beside the priors and are never added to them.
Questions about plugins
- Why does my browser report plugins I never installed?
- Browsers keep a fixed list of PDF viewer entries for compatibility with old pages. The list is the same on almost every install, which is the point.
- Why would an empty list be a problem?
- Real desktop Chrome always reports the fixed list. An empty one is typical of headless and automated builds, and detectors check for it.
In the same group
Next
Display preferences: The colour scheme, contrast, reduced-motion and forced-colours media queries the browser reports.
Where the pens move
A value patched in the page is a patched value. Set in the engine, it is just a value.
Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.
It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.
Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.