CodeSampleX

Recordscargochrono0.4.39chrono::FixedOffset::east_opt

Change the conditions
Fixed
Symbolchrono::FixedOffset::east_opt
Filter OSalpine musl Runtimerust 1 Package version0.4.39 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

chrono::FixedOffset::east_opt @0.4.39alpine musl · x64 · rust 1 · cargo · rust

3 of 3 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
1 / 1
Contract verifications
3 / 3
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Unknown 1 · Steady 5

All 5 dependencies report steady passing evidence.

Library Version Health Measured there Projects
android-tzdata 0.1.1 UNKNOWN No linked outcome measured nothing measured 1 project-day
iana-time-zone 0.1.65 PASS All observations passed builds observed 1 project-day
js-sys 0.3.104 PASS All observations passed contract passed 1 project-day
num-traits 0.2.19 PASS All observations passed contract passed 1 project-day
wasm-bindgen 0.2.127 PASS All observations passed contract passed 1 project-day
windows-targets 0.52.6 PASS All observations passed contract passed 1 project-day

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 0 · unchanged at every release: 8

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.