inikulin/parse5

HTML parsing/serialization toolset for Node.js. WHATWG HTML Living Standard (aka HTML5)-compliant.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 17th, 2026
Created on March 18th, 2013
Open Issues & Pull Requests: 38 (+0)
GitHub issues: Enabled
Number of forks: 257
Total Stargazers: 3,933 (+0)
Total Subscribers: 40 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.0 hours
Mean response time: 77.9 days
90th percentile: 31.8 days
Tracked items: 23

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 626 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • breaking (1)
  • enhancement (1)
  • testing (1)

Detailed Description

parse5 is an HTML parsing and serialization toolset for Node.js that implements the WHATWG HTML Living Standard specification.

The tool solves the problem of parsing HTML in a way that matches how modern browsers handle it. Rather than using simplified parsing logic, parse5 implements the full WHATWG specification algorithm, which means it handles edge cases, error recovery, and quirks modes the same way browsers do. This approach ensures that HTML parsed by the tool will behave identically to how a browser would interpret it. The toolset provides both parsing capabilities to convert HTML strings into document trees and serialization capabilities to convert those trees back into HTML strings.

Developers should choose parse5 when they need spec-compliant HTML parsing in Node.js environments where browser-like behavior matters. It suits projects that require accurate HTML manipulation, such as server-side rendering, static site generation, or HTML analysis tools. The tool is particularly valuable for projects that cannot tolerate parsing differences between the tool and actual browsers, making it ideal for testing frameworks, DOM implementations, and HTML processors that need to match browser semantics exactly.

The project maintains active test coverage and passes continuous integration checks. Development activity shows consistent attention to specification compliance and reliability across the codebase.