microsoft/tsdoc

A doc comment standard for TypeScript

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Type:Documentation / SpecificationCategory(s):Documentation ToolsCode Quality & Static AnalysisDeveloper Tools
Added to GitGenius on September 13th, 2026
Created on March 1st, 2018
Open Issues & Pull Requests: 157 (+0)
GitHub issues: Enabled
Number of forks: 162
Total Stargazers: 4,970 (+0)
Total Subscribers: 47 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 days
Mean response time: 98.5 days
90th percentile: 325.2 days
Tracked items: 31

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 29
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 1,501 days
Stale 30+ days: 27
Stale 90+ days: 23

Recent activity

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

Top labels

  • request for comments (5)
  • octogonz-parser-backlog (3)
  • effort: medium (1)
  • enhancement (1)
  • needs design (1)
  • needs more info (1)
  • tool scenario (1)

Detailed Description

TSDoc is a standardized doc comment format for TypeScript that provides a specification and parser for structured documentation in code.

The tool addresses the fragmentation of documentation comment styles in TypeScript projects by establishing a unified standard similar to JSDoc but designed specifically for TypeScript's type system. It works by defining a formal specification for doc comment syntax, including standard tags like @param, @remarks, and @alpha, and providing a parser library that can read and validate these comments programmatically. This allows tools and documentation generators to reliably extract and process documentation from TypeScript source files.

Teams should adopt TSDoc if they maintain TypeScript libraries or large codebases where consistent, machine-readable documentation is important. It suits projects that want to enforce documentation standards across a team or integrate documentation generation into their build pipeline. The project includes an ESLint plugin for linting doc comments, a parser library for programmatic access, and a configuration loader for customizing TSDoc behavior per project. An interactive playground is available for learning the syntax and testing the parser.

The project maintains an active monorepo structure with separate packages for the core parser, ESLint integration, and configuration handling. Development includes regular updates to the changelog across multiple packages, indicating ongoing maintenance and refinement of the specification and tooling.