core

stackblitz/core

Online IDE powered by Visual Studio Code ⚡️

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
Jun 9, 2024
854 days ago
Stars, last 7 weeks
Stars, weekly: 10,889 → 10,893 (Sep 29 – Oct 6, 2026)
History starts 2026-09-29, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
10.9K
Forks
1.3K
Open issues
848
Watchers
229
Primary language
Unspecified
Created
Jun 15, 2017
Owner
stackblitz · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. This repo does not expose a primary language.

Topics

This repository has no GitHub topics.

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 66%, self-hostable 24%, hosted offering 72%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, added by hand. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2024-06-09This is the badge for stackblitz/core, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/stackblitz/core.svg)](https://ossean.com/stackblitz/core)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.