Install tidy-html5 with Homebrew, apt, dnf, winget, MacPorts, pacman, scoop, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• tidy

Project history

The official HTML Tidy site traces the project to Dave Raggett of the W3C in the early Web era. Raggett's original W3C page describes Tidy as a free utility for automatically fixing common HTML mistakes, cleaning up hard-to-read output from editors and converters, and identifying accessibility issues that need author attention.

After Raggett's original work, maintenance moved to volunteers at tidy.sourceforge.net, where the project became a C library and kept pace with evolving standards. The official history says W3C members renewed interest in 2011 and forked the project to GitHub with HTML5 compatibility, then in 2015 HTACG formed to revitalize Tidy after a non-maintained period.

HTACG's repository carries the modern `tidy-html5` source and describes the project as the granddaddy of HTML tools with support for modern standards. The repository metadata shows the GitHub project dating to 2011, matching the official history's GitHub-era transition.

Adoption history

HTML Tidy has unusually broad package-manager and platform history for a web utility. The official site says many operating systems already ship a `tidy` command, though often too old for HTML5, and lists package-manager installs for macOS through Fink, Homebrew, and MacPorts plus Windows through Chocolatey.

The input package facts show a wider current packaging footprint across Homebrew, Debian/Ubuntu, Fedora, Arch, MacPorts, Scoop, winget, and openSUSE-family packages, reflecting Tidy's role as both a CLI utility and `libtidy` development dependency.

How it is used

Users run `tidy` to clean malformed or messy HTML, format output, flag errors and warnings with line and column information, and modernize documents produced by WYSIWYG editors or office exporters. Developers can also embed `libtidy`, whose official site describes APIs for parsing HTML into a DOM-like tree, cleaning and diagnostics, traversing nodes, and pretty-print output.

The original W3C page also documents Tidy's Unix-tool-style appeal: it can be used locally as a binary, as source code, and historically through online services, making it useful in editors, build scripts, validation workflows, and conversion pipelines.

Why package nerds care

For package nerds, tidy-html5 is a good example of an old web utility whose name, fork history, and packaging split matter: users may see `tidy`, `tidy-html5`, `libtidy`, or development packages depending on the platform.

It is also historically important because it bridges early W3C-era authoring tools and modern HTML5-oriented command-line workflows. The package remains useful precisely because it is boring, scriptable, and available almost everywhere.

Timeline

• 1998: HTML Tidy copyright history begins in the project license files.
• 2000: Raggett's W3C page had already handed maintenance to SourceForge volunteers.
• 2011: W3C members forked Tidy to GitHub for renewed work and HTML5 compatibility.
• 2015: HTACG formed to revitalize the project and received W3C project ownership.
• 2024: HTACG tidy-html5 repository metadata shows continued GitHub activity.

Related projects

• Related project surfaces include Dave Raggett's original W3C Tidy page, the SourceForge-era tidy project, the W3C GitHub fork, the HTACG tidy-html5 repository, and downstream packages named `tidy`, `tidy-html5`, or `libtidy`.

Sources

• https://api.github.com/repos/htacg/tidy-html5
• https://api.html-tidy.org/tidy/tidylib_api_5.1.25/history.html
• https://github.com/htacg/tidy-html5
• https://github.com/htacg/tidy-html5/blob/next/README/LICENSE.md
• https://www.html-tidy.org/
• https://www.w3.org/People/Raggett/tidy/
• input source_facts.package-manager