Recordscargowindows-targets0.52.6
Environment detail
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 |
|---|---|---|---|---|---|---|
| unknown · Rust · cargo · linux glibc
Observations: PROJECT_COMPILE 0✓ 2✕ · PROJECT_PROCESS 5✓
|
ELEVATED FAILURE | 7 | 0 | 71% | 1 | 2026-09-16 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 3✓ — Verified: CONTRACT 1✓
|
LOW | 4 +3 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 ×1 0.52.6 os=linux sha256:3bab2c36697a…error: could not compile `sample-windows-sys` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16
-
observed PROJECT_COMPILE exit 101 E0432 ×1 0.52.6 os=linux sha256:ab5c9e467e95…error[E0432]: unresolved import `windows_sys::Win32::Foundation::HRESULT`rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16
Symbols
No symbols with evidence yet.
Published samples
- windows-targets 0.52.6 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. HOW MIT-0 · 2026-09-16