Discofork
Repository brief

microsoft/TypeScript

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:23:29.224Z
3mo ago

microsoft/TypeScript

microsoft/TypeScript is the upstream TypeScript compiler/runtime repository: a large, active, non-archived open source project with 108,348 stars and 13,307 forks. It ships the `typescript` npm package, provides `tsc` and `tsserver`, and is currently in a maintenance-focused state where code changes are limited to a small set of fixes while most bug fixes are directed to `typescript-go`.

GitHub
Loading tags...
Stars108,348
Forks13,307
Default branchmain
Last pushed2026-03-28T00:22:52Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Choose this fork only if you need this historical JSX support and are willing to live without modern TypeScript maintenance. For most users, upstream TypeScript is the better default because this fork is far behind and appears effectively unmaintained.

Choose this fork only if you specifically need ExtJS-compatible class emission on an old TypeScript 1.8 baseline. For anything else, upstream TypeScript is the better default because this fork is heavily outdated and materially behind current compiler, tooling, and maintenance work.

Prefer this fork only if you need Bloomberg's historical branch state or internal collaboration workflow. For normal TypeScript development, tooling, or adoption, upstream is the better default because this fork is stale and significantly behind.

Choose this fork only if you already depend on its historical customizations. For new work or general TypeScript use, upstream is the safer choice because this fork is stale and far behind current maintenance.

Prefer this fork only if its custom TypeScript semantics are the product requirement. If you want current fixes, lower maintenance risk, or mainstream compatibility, upstream is the better default.

Choose the fork only if you need its legacy compiler/test behavior or its bespoke automation. If you want current TypeScript, this fork is too stale and too far from upstream to be a low-risk starting point.