scriptc: a TypeScript-to-native compiler from Vercel

TL;DR: scriptc is a Vercel Labs project described in a single line as a TypeScript-to-native compiler. It is Apache-2.0, was created on 2026-07-22, and picked up 5,423 stars in the ten weeks before this post, which makes it one of the fastest-rising developer repositories on GitHub right now.

What it is

The repository description is the whole pitch: “TypeScript-to-Native Compiler”. It lives under the vercel-labs organisation, which is worth noting on its own, because that org ships a lot of infrastructure tooling that other teams quietly end up depending on.

What the API reports, in full:

Field	Value
Full name	vercel-labs/scriptc
Description	TypeScript-to-Native Compiler
Language	TypeScript
License	Apache-2.0
Stars	5,423
Forks	141
Open issues	54
Created	2026-07-22
Last push	2026-09-28
Homepage	scriptc.dev

Notice what is missing. This repository carries no GitHub topics at all, which is unusual for a project attracting this much attention. The description also names no target platform, no output format, and no supported language pair. The metadata tells you less here than it would for a comparable repository, so read the specifics off the project page rather than taking them from anyone’s summary.

The velocity is the story

Created 2026-07-22, last pushed 2026-09-28. That is roughly ten weeks, and 5,423 stars over ten weeks works out to about 80 stars a day, sustained rather than spiked.

Star velocity is a poor measure of quality and a decent measure of attention. A number running this high usually means one of three things: a large platform company attached to the project, a real problem a lot of people want solved, or both. The vercel-labs namespace plus a fork count of 141 that is still climbing suggests a mix of the two.

The 54 open issues against 5,423 stars is a healthier ratio than most repositories this age manage. For something ten weeks old, that reads as either good triage or as issues clustered early around setup and first use.

How to look at it yourself

The project site is scriptc.dev. From a terminal you can get the README without opening a browser:

gh repo view vercel-labs/scriptc

If you want the same metadata this post is built on, it is one call away:

gh api repos/vercel-labs/scriptc \
  --jq '{stars: .stargazers_count, license: .license.spdx_id, created: .created_at, pushed: .pushed_at}'

To follow the source:

git clone https://github.com/vercel-labs/scriptc.git
cd scriptc
ls

The detail I would check first, after cloning, is that the primary language is TypeScript while the project is a compiler. A compiler written in the language it consumes is a real design choice with real tradeoffs, and whether scriptc leans on an existing parser or ships its own becomes obvious from the tree within a minute.

When to use it

scriptc is worth a look if you ship TypeScript and have a reason to want a native artifact instead of shipping a JavaScript runtime. The Apache-2.0 license means commercial use is not a question you have to answer first, which removes the most common reason people hesitate.

Hold off on committing if what you need is a mature, well-documented toolchain. A ten-week-old compiler from a young repository is a research bet, not infrastructure. And given that the description does not say what it emits or what it accepts, treat it as something you evaluate, not something you migrate onto.

Source and Accuracy Notes

• Project page: https://github.com/vercel-labs/scriptc
• Homepage: https://scriptc.dev
• Source repository: vercel-labs/scriptc (verified via GitHub API html_url)
• License: Apache-2.0 (verified via GitHub API license.spdx_id)
• Stars at time of writing: 5,423