Jump to content

Open washing

From Consumer Rights Wiki

⚠️This article has been marked as incomplete. Sourcing or verifiability needs additional work.

A moderator needs to check the page before this notice can be removed. Visit the noticeboard or the #appeals channel in either Zulip or Discord to request removal.
More info ▼

Articles must provide verifiable, credible evidence for their claims and avoid relying on forum posts, personal blogs, or other unverifiable sources. You can help by replacing weak citations with reputable reporting, corporate communications, receipts, repair logs, or independent investigative coverage that demonstrates the systemic relevance required by the Mission statement and Moderator Guidelines.

🧽🫧This article needs cleanup. It contains sources and content but lacks proper formatting/structure.

More info ▼

Common issues include not following the correct preload outline (incident, company, product), references that don't use <ref></ref> or Cite web, leftover "WIP" markers, or long quotes not wrapped in Quote. You can help by applying the relevant preload sections, converting raw URLs into proper citations, and removing editor notes.

Open washing is a marketing tactic that superficially associates a product with a widely trusted open-source software culture when the product itself does not provide freedoms that define that culture.[1]

How it works

[edit | edit source]

There can be multiple tricks used for this deception, including:

  • A website design that draws similarities from an open source developing platforms (e.g. GitHub star badge).
  • Public source code consist of compiled binary files.

Why it is a problem

[edit | edit source]
  1. Falsely rendering themselves as transparent and trustworthy which may deceive consumer into less caution while handling the software.
  2. Application can perform unnecessary or malicious commands on host systems.

What doesn't fall under this theme

[edit | edit source]
  • Use of a software forge commonly associated with open source software, such as GitHub, GitLab and Codeberg, without publishing the source code there as well; e.g. only publishing software packages for distribution or using its issue tracker to collect bug reports and to publish future development plans
  • Hijacking websites designed by malicious attackers. (This doesn't have anything to do with developers of the real application)[2]

Examples

[edit | edit source]
  • The pictures shows Top of the BetterDisplay Pro website. It consists of a GitHub star badge, links for releases, issues, discussion and wiki on left. And on right there's a button for get pro version and a button for download. The download button directly downloads the application.
    The pictures shows Top of the BetterDisplay Pro website.
    BetterDisplay Pro is an application for display settings. Their website design are similar to open source projects' websites.[3] It has GitHub star badge. On their repository no part of source code is available.[4] Download button directly downloads the program from GitHub. There is no indication that the application is close source on the website.
  • Knockoff - Browser extension that gave interviews regarding its open-source nature and no telemetry data collection. In the same month it released, the project went closed-source and started to collect telemetry data on its users due to auto-updates on browser extensions.

References

[edit | edit source]
  1. "Open Washing". Is it really foss?. Retrieved 2026-08-09.{{cite web}}: CS1 maint: url-status (link)
  2. Bukhteyev, Alexey (2026-06-03). "Impersonation, Click Hijacking, and TDS: Inside a Malware Distribution Ecosystem".
  3. "BetterDisplay Pro | Unlock Your Mac Displays".
  4. [1]