Ross ROSS = Recommend OSS · open-source software intelligence for agents

tc39/proposal-signals resource

A proposal to add signals to JavaScript. observed · 2026-08-28

github.com/tc39/proposal-signals · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

57/100

  • Activity 64
  • Release rhythm 35
  • Longevity 79

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 1115
  • days_rel: n/a
  • days_push: 220
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

4174 stars · 73 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

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

learning-resource · maturity experimental

state-management frontend-framework developer-tools web-development frontend programming-languages developer-tools browser cross-platform tc39 javascript-proposal signals reactivity stage-1 specification ecmascript polyfill nodejs

1 source

Member repositories

RepositoryRoleHealth v2
tc39/proposal-signalsmain57

For agents

markdown · JSON · MCP: product_card(name="tc39/proposal-signals")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem