CodeSampleX

Recordscargochrono0.4.45chrono::DateTime

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

Current conditions

chrono::DateTime @0.4.45alpine musl · x64 · rust 1 · cargo · rust

1 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (1)

Project observations
0 / 1
Contract verifications
1 / 2
Independent reporting peers
1
Failures with a captured fingerprint
0 / 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

Observed problems 1 · Steady 3

First observed break

0.4.45

linux · rust@1 · executionContext=rust

1 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
num-traits 0.2.19 PASS All observations passed contract passed 1 project-day
serde 1.0.229 PASS All observations passed contract passed 2 project-days
serde_json 1.0.151 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.

Recent failure clusters