unifiedjs/unified

Parse, inspect, transform, and serialize content with syntax trees

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 13th, 2026
Created on July 31st, 2015
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 129
Total Stargazers: 5,030 (+0)
Total Subscribers: 32 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.4 hours
Mean response time: 2.2 hours
90th percentile: 6.2 hours
Tracked items: 5

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 5% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • 👎 phase/no (6)
  • 👯 no/duplicate (2)
  • 🤷 no/invalid (2)
  • ☂️ area/types (1)
  • 👀 no/external (1)
  • 💬 type/discussion (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

unified is a syntax tree processor that lets you parse, inspect, transform, and serialize content with plugins.

The tool solves the problem of working with structured representations of content by providing a unified interface for processing abstract syntax trees. It works by accepting content, parsing it into a tree structure, running transformations through a plugin system, and serializing the result back to a string. The core processor accepts plugins that can inspect or modify the tree at any stage, and supports both synchronous and asynchronous workflows.

You should use unified when building tools that need to inspect or transform content programmatically. It suits projects like site generators, linters, code formatters, or any system that needs to work with multiple content types. If you are working with a single content type like markdown, the specialized ecosystem packages built on unified (such as remark for markdown, rehype for HTML, or retext for natural language) may be more convenient. However, unified itself is the right choice when you need to handle different kinds of content together or want to compose utilities across multiple ecosystems.

The project maintains a large ecosystem of packages built around it and receives ongoing maintenance with active plugin development. The tool is widely adopted in established projects and continues to be used as a foundation for content processing workflows across different domains.