Who Really Owns JavaScript? Inside the Deno vs Oracle Trademark Battle

JavaScript is a beloved language that powers the modern web, but its ownership is now contested.

Oracle, which acquired Sun Microsystems, claims the "JavaScript" trademark, while Deno has filed a lawsuit in 2024 challenging that claim.

Figure 1 JavaScript ecosystem

The story goes back to 1995 when Netscape needed a scripting language for its browser, leading Brendan Eich to create a language initially called "Mocha", then "LiveScript", and finally "JavaScript" as a marketing move linking it to Java.

Figure 2 Netscape engineer Brendan Eich

The name became a valuable asset for Sun Microsystems and later Oracle after its acquisition, even though Oracle has not actively developed the language.

How the lawsuit began

In September 2022, Deno’s creator Ryan Dahl and JavaScript architect Brendan Eich published an open letter urging Oracle to abandon the trademark.

More than 14,000 developers signed the petition, demanding that JavaScript remain a public asset.

The petition challenges three key points:

JavaScript is a generic term – It is defined by the ECMA‑262 specification and belongs to the global developer community, not any company.

Fraudulent renewal – Deno alleges Oracle submitted false evidence in 2019 to extend the trademark, using a screenshot from the Node.js site that has no connection to Oracle.

Trademark abandonment – Oracle has barely used the trademark since acquiring it in 2009; under U.S. law, non‑use for three consecutive years can lead to abandonment.

If Oracle wishes to keep the trademark, it must provide evidence of active use by January 2025.

Predictions: outcomes and impact

If Deno wins

Freedom of use – Developers could freely use the term "JavaScript" without legal concerns.

Empowering the community – The victory would reinforce open‑source values, showing that shared resources can be reclaimed from corporate claims.

Simplified terminology – Confusion between "JavaScript" and "ECMAScript" would diminish, making learning materials clearer.

If Oracle wins

Figure 4 Coding environment

Developers would continue facing legal uncertainty, official documentation would keep using "ECMAScript", and community projects might avoid the name "JavaScript".

Community morale could suffer, portraying Oracle as an obstacle to progress, and smaller companies might shy away from using the term, stifling innovation.

The case would set a precedent for how open‑source technologies balance corporate interests and community ownership.

Regardless of the outcome, the dispute highlights that JavaScript's true legacy lies with the millions of developers who have built and evolved it, not merely its name.