Download websites that use Yett

About Yett

Consent banners are easy to add to a page. Blocking the third party scripts sitting behind them is the part teams get wrong, and Yett was written for that gap. The library intercepts script tags whose sources match a blocklist and refuses to let them execute until the page signals that consent has arrived. A site carrying it has made a deliberate engineering choice, since enforcement happens in the page, at the moment of execution, instead of relying on a tag manager to behave.

Published under the MIT license in 2018 and written in JavaScript, Yett belongs to a familiar species of dependency, the small single purpose file a developer drops in once and never revisits. The version record reflects that habit. Installs concentrate on 0.2.3 out of 3 releases we can tell apart, and the numbering has not yet crossed into a first stable line. Nobody upgrades a script blocker that keeps working, so the version spread here measures how long ago each site's consent layer was built rather than how actively the project is maintained.

As of October 2026 we detect Yett on 16 sites, and the honest reading of that figure is that it is a floor. A blocker of this size is frequently pulled into an application bundle, minified alongside everything else, and once that happens there is no separate file left to fingerprint. Sites that load it as its own asset are visible. Sites that compile it into a bundle are not. Anyone treating our count as the full population will undercount, and the direction of the error is predictable, because the more sophisticated the build pipeline, the more likely the trace disappears.

What survives detection is still worth having, because the sites that remain visible are the ones that assembled a consent stack by hand. Consent management vendors care about that group, which is a set of teams who solved script blocking themselves and therefore never bought a platform to do it. Compliance auditors care for the opposite reason, since hand rolled enforcement is where blocklists go stale and new tags slip through unblocked. Privacy researchers get something rarer, a sample of sites where blocking is technically real rather than cosmetic.

A per domain lookup answers whether one site holds scripts back until consent arrives. The downloadable list answers the questions that need the whole set at once. Which markets and which platform stacks produce hand built consent enforcement, whether these sites also carry a commercial consent platform in the same row, and whether the population is shrinking as teams migrate to managed tools. Every row arrives with the rest of the technologies found on that domain, so the blocking library can be read next to the analytics and advertising tags it was installed to hold back.