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

tc39/proposal-temporal

Provides standard objects and functions for working with dates and times. observed · 2026-08-28

github.com/tc39/proposal-temporal · homepage · HTML · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

65/100

  • Activity 94
  • Release rhythm 8
  • Longevity 100

Flags: no_license

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: 3462
  • days_rel: n/a
  • days_push: 37
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

3709 stars · 177 forks observed · 2026-08-28

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

The TC39 Temporal proposal, a Stage 4 ECMAScript standard adding a modern date and time API to JavaScript as a global namespace object with immutable types for dates, times, durations, and timezone-aware values. The repository hosts the specification text, documentation, cookbook, and a polyfill, and will be archived once merged into ECMA-262/ECMA-402.

Use cases

  • work with dates and times in javascript without the legacy Date pitfalls
  • do timezone-aware and DST-safe date arithmetic
  • parse and format ISO 8601 / RFC 3339 date-time strings
  • support non-Gregorian calendars like Hijri or Nepali
  • convert timestamps between time zones
  • schedule meetings across time zones
  • represent date-only or time-only values without implicit timezone assumptions
  • replace moment.js or date-fns with a built-in API

When to choose

  • you need a standards-track, immutable date/time API in JavaScript with first-class time zone and calendar support
  • you are targeting environments where Temporal is shipped (Firefox 139+, Chrome 144+, Node 26+) or can use the polyfill
  • you want DST-safe arithmetic and strict string parsing instead of legacy Date quirks

When to avoid

  • you only target runtimes without Temporal support and cannot ship a polyfill
  • you need leap-second precision, which Temporal intentionally ignores
  • you need a mature third-party library ecosystem with plugins beyond what the standard API provides

Facets

library · maturity stable

date-time programming-languages developer-tools browser cross-platform ecmascript tc39 javascript temporal timezones calendars dst polyfill language-proposal stage-4 localization nodejs

10 sources

Member repositories

RepositoryRoleHealth v2
tc39/proposal-temporalmain65

For agents

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

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