Signalcrest
← Back to feed
devtosecurity

I Deployed a Purple Team Inside My Kubernetes Cluster. The Scanners Never Saw It Coming.

Kubernetes security scanner evasion

Steady

9

signal score

🔗 2

sources · k8s

→ Steady

7-day est. ~11

ShareLinkedInOpen source ↗

Why this scored 9

every term, weighted
Velocity+0.1 / 40 max

Engagement per hour, normalized against the fastest item on its own source

Acceleration+0.0 / 25 max

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+2.8 / 25 max

How many independent communities are talking about the same entity

Recency+7.9 / 10 max

Decays to zero over 14 days

Saturation penalty−1.3 / 30 max

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite9.4

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement. Full methodology

Outlook

low confidence · estimate, not a guarantee

7-day

~11

range 9–13

14-day

~11

range 8–13

30-day

~11

range 7–14

Signal history

7-day window (free)

— — projected trajectory (estimate, not a guarantee)

Entities

k8spurpleteam
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/dev%3A4217624)](https://www.signalcrest.app/topic/dev%3A4217624)

Drop this in a README or blog post — it updates automatically as the score moves.