arrayref
for rust developers, security engineers
Why this scored 8
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 130
Supply chain attack on arrayref
New supply-chain attack discovered in the Rust arrayref crate. · for Rust developers
lobstersSteady 2 · arrayrefsecurity52d ago - 219
Rust malware in arrayref: how a build.rs ran a payload at compile time
A malicious build.rs in the arrayref crate can execute payloads at compile time. · for rust developers, security engineers
devtoSteadysecurity11d ago - 315
Malicious Rust crate Arrayref runs a build-time payload
Malicious Rust crate arrayref can execute payloads at build time, raising supply-chain risk. · for Rust developers
hackernewsSteadysecurity52d ago