Recordscargozerofrom-derive0.1.7ZeroFrom
shared with 2 packages — this evidence cannot say whose API it is
Published samples
- zerofrom-derive 0.1.7: ZeroFrom 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. HOWZeroFrom MIT-0 · 2026-11-06
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 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-11-11 |
snapshot · 2026-11-11
Failure clusters
-
observed PROJECT_COMPILE exit 101 ×1 0.1.7 os=linux sha256:6ab2a1478c5d…error: could not compile `sample-zerofrom-derive` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-06 · Last seen: 2026-11-06