JSON Formatter extension archived and moving closed‑source — users say new build is injecting adware

What changed?

The popular JSON Formatter Chrome extension’s GitHub repo is now marked ARCHIVED and the author says development is moving to a closed‑source, commercial model. The maintainer has published a final open‑source snapshot called JSON Formatter Classic and suggests users who want a simple, local‑only formatter switch to that; the original README walks through features, install options and the move to a commercial API‑browsing product. Simple enough on paper. But not everyone is happy.

Reports of adware activity

It has been reported that the more recent, closed‑source distribution of the extension is allegedly injecting adware or unwanted advertising into pages where it runs. Those claims are coming from users on community forums; they have not been independently verified in this article. Still — when an extension that parses your API responses starts mutating pages or adding ads, alarms should go off. Trust, once broken, is hard to stitch back together.

Why it matters

Browser extensions run with powerful privileges; they see and can modify page content, network requests, even credentials in some cases. For developers and ops folks who used JSON Formatter to peek at API responses, the idea that a formerly open tool might now be closed‑source and inserting third‑party content feels like a betrayal. Open source offered transparency. Closed source? You’re left guessing what the code actually does.

What to do

If you’re worried: uninstall the closed build, install JSON Formatter Classic from the Chrome Web Store or load the unpacked, source-built copy described on the repo, or switch to an alternative open tool. Review extension permissions, inspect network traffic, and report suspicious behavior to the Chrome Web Store. No silver bullet — but a healthy dose of skepticism and a backup plan will do wonders.

Sources: github.com/callumlocke, Hacker News