Recordscargochrono0.4.45chrono::Duration
shared with 3 packages — this evidence cannot say whose API it is
Published samples
- chrono 0.4.45: Disabling chrono default features strips Utc::now and Local which require the clock feature rather than std, while serde support requires an explicit opt-in serde feature and serializes DateTime as an RFC 3339 string This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWchrono::DateTimechrono::Utcchrono::NaiveDatechrono::NaiveTimechrono::NaiveDateTimechrono::Durationrust MIT-0 · 2026-08-15
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_TEST 0✓ 1✕ — Verified: CONTRACT 1✓ 1✕
|
ELEVATED FAILURE | 1 | 2 | 48% | 1 · 2✓ | 2026-09-08 |
snapshot · 2026-09-15
Failure clusters
-
observed PROJECT_TEST Evidence gap ×1 0.4.45 executionContext=rust · os=linux · runtime=rust@1 chrono::DurationEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-08 · Last seen: 2026-09-08