chronotope/chrono
Date and time library for Rust observed · 2026-08-28
Health v2 · maintenance only
89/100
- Activity 95
- Release rhythm 75
- 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-02. Adoption (stars, forks) is never an input.
- gap_med: 89.5
- age_days: 4541
- days_rel: 90
- days_push: 30
- n_releases_24m: 7
Adoption not part of the score
3900 stars · 610 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Chrono is a date and time library for Rust providing timezone-aware DateTime types, timezone-naive variants, and strftime-style parsing and formatting. It focuses on correct operations in the proleptic Gregorian calendar with configurable feature flags for minimal binary size.
Use cases
- parse and format dates in rust
- handle timezones correctly in rust
- get current system time and local timezone
- convert between utc and local time
- parse timestamps from strings
- do date arithmetic like adding days or months
When to choose
- you need correct, timezone-aware date and time handling in Rust
- you want mature, widely used date/time crate with huge ecosystem adoption
- you need configurable features to keep binaries small
When to avoid
- you need non-Gregorian calendars
- you need full leap second support
- you need bundled timezone data without a companion crate
Facets
library · maturity stable
date-time developer-tools cross-platform rust cross-platform wasm calendar timezone strftime-parsing no-std-friendly
2 sources
- readme: https://github.com/chronotope/chrono · fetched 2026-08-28 · 37546c926e53
- registry_crates: https://crates.io/api/v1/crates/chrono · fetched 2026-08-29 · 37c770a9539b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| chronotope/chrono | main | 89 |
For agents
markdown · JSON · MCP: product_card(name="chronotope/chrono")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem