# tc39/proposal-signals

A proposal to add signals to JavaScript.

Repository: https://github.com/tc39/proposal-signals
Canonical: https://ross.abutalabs.com/products/proposal-signals
License: MIT
License Family: permissive
Last push: 2026-01-25T20:23:21+00:00

## Health v2 (maintenance only)
Score: 57/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 64, release rhythm 35, longevity 79
- inputs: {"age_days": 1115, "days_push": 220, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4174, forks 73 (observed 2026-08-28T04:08:38.109605+00:00)

## What it is
A TC39 Stage 1 proposal to standardize a signals primitive for JavaScript, defining the core semantics of a reactive signal graph rather than a developer-facing API. It is intended as a common foundation that frameworks like Angular, Vue, Solid, Svelte, and Preact can build their reactivity systems on, with a polyfill available for experimentation.

## Use cases
- standardize reactive state management in javascript
- build a framework reactivity core on a shared signal graph
- track how the tc39 signals proposal is progressing
- experiment with signals via a polyfill before standardization
- align signal implementations across javascript frameworks
- understand the proposed semantics for computed and reactive values

## When to choose
- You are a framework author evaluating a common underlying signal graph to back your reactivity system
- You want to follow or contribute to the standardization effort for signals in JavaScript
- You need interoperable reactive state primitives across multiple frameworks
- You want to prototype against the proposed semantics using the companion polyfill

## When to avoid
- You need a production-ready signals library with a stable developer-facing API today
- You expect the proposal's API to remain unchanged, since it is still Stage 1 and may evolve significantly
- You just want reactive state in an app without caring about framework interoperability or standardization
- You need a finished ECMAScript feature - this is not yet part of the language standard

## Facets
- artifact type: learning-resource
- maturity: experimental
- function: state-management, frontend-framework, developer-tools
- domain: web-development, frontend, programming-languages, developer-tools
- platform: browser, cross-platform
- tags: tc39, javascript-proposal, signals, reactivity, stage-1, specification, ecmascript, polyfill, nodejs

## Member repositories
- tc39/proposal-signals (main) score 57

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:38.109605+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:22:43.622411+00:00, confidence not recorded.
  - readme: https://github.com/tc39/proposal-signals (fetched 2026-08-28T04:08:38.109605+00:00, sha 1b7faae956e7)
- Data as of 2026-08-30T08:39:29.467469+00:00.