Web Environment Integrity (WEI) is an abandoned API proposal previously under development for Google Chrome.[1] A Web Environment Integrity prototype existed in Chromium,[2][3] but was removed in November 2023 after extensive criticism by many tech groups.[4] Its purpose was to verify that interactions with websites were human and authentic as defined by third-party attesters.
The draft proposed an API for websites to get a digitally signed token that contains the certifier's name and whether or not they deem the web client to be authentic. The stated goal was for sites to be able to restrict access to human users instead of automated programs and "allow web servers to evaluate the authenticity of the device and honest representation of the software stack and the traffic from the device". Access to this API would not be allowed in non-secure (HTTP) contexts.[5]
The proposal first showed up as a commit to Chromium in April before being announced by its developers, Google engineers, in May. It received a few concerned comments from those who followed the browser's rendering engine's development. After discussion at W3C in late April, its working draft specification was published as part of the process to develop standards for the web on July 21, 2023. As a result, users flooded the proposal's GitHub repository with critical comments and flaming of the proposal's authors. As a result, the Google engineers limited comment to those who have contributed to the repository and added a code of conduct.[6] On the same day, Chromium's preliminary code to implement the standard was enabled.[2]
On November 2, 2023, Google abandoned the proposal, removed the prototype implementation from Chromium, and proposed a replacement API named "Android WebView Media Integrity API" limited to WebViews on Android. Google plans to start testing the new API with partners in early 2024.[4]
The proposal received widespread criticism for limiting general purpose computing, with some comparing WEI to digital rights management (DRM).[7] Others have accused the standard of being evidence of Google abusing Chrome's near-monopoly of browser share.[6] Some have issued official statements on the matter in 2023: