DavidAnson/markdownlint

A Node.js style checker and lint tool for Markdown/CommonMark files.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 15th, 2015
Open Issues & Pull Requests: 79 (+0)
GitHub issues: Enabled
Number of forks: 944
Total Stargazers: 6,339 (+0)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 hours
Mean response time: 70.8 days
90th percentile: 7.5 days
Tracked items: 204

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 2 hours, while "new rule" waits about 6 days. Only 10% of issues opened in the past year have been closed. Three people close 70% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 31
New in 7 days: 0
Closed in 7 days: 4
Avg open age: 915 days
Stale 30+ days: 29
Stale 90+ days: 27

Recent activity

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

Top labels

  • question (85)
  • enhancement (46)
  • fixed in next (40)
  • new rule (20)
  • bug (8)

Detailed Description

markdownlint is a style checker and lint tool for Markdown files that runs on Node.js.

The tool addresses inconsistency and style issues in Markdown documents by applying configurable rules that check for common problems like spacing, formatting, and structural violations. It works by parsing Markdown files against a set of built-in rules, each targeting specific style concerns, and reporting violations with their locations and descriptions. Users can customize which rules apply to their projects and configure rule parameters to match their preferred Markdown style.

Developers should choose markdownlint if they want to enforce consistent Markdown formatting across a project or documentation set. It suits projects with multiple contributors where style consistency matters, documentation repositories, and teams that want to catch formatting issues before content is merged. The tool integrates into development workflows through command-line usage and can be incorporated into CI/CD pipelines to validate Markdown files automatically.

The project shows steady maintenance with regular updates addressing bug fixes and rule improvements. Development activity includes responsiveness to reported issues and incorporation of community feedback into rule refinements. The tool receives ongoing enhancements to its rule set and configuration options based on user needs.