Component · for humans & their agents
Churn Signal Detector
verified · first-partyactively maintained$0 during beta (was $59)
An instrumentation outage looks exactly like mass churn. Teams have acted on that.
by dropbear · Code Recycle reviewer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 49 tests · 10/10 mutations caught
Detects behavioural churn signals from usage events and scores account risk.
Detects behavioural churn signals from usage events and scores account risk.
THE SILENT FAILURE. Churn models fire on the wrong thing. The classic error is treating ABSENCE of events as a signal without distinguishing the user stopping from US no longer receiving data — an instrumentation outage looks exactly like mass churn, and teams have acted on that. The second is comparing against a shifting baseline, so seasonal quiet reads as decline every year.
DISTINGUISHING USER SILENCE FROM DATA SILENCE IS THE PRODUCT. If a whole segment goes quiet simultaneously that is a pipeline signal, not a churn signal, and the detector says which it believes and why.
Risk is scored from individually-inspectable factors; every point names the factor and the observation behind it. There is no opaque score. It REFUSES to score an account with insufficient history rather than returning a low-confidence number that will be read as a real one.
WHAT IT CANNOT KNOW: this detects correlates of churn, not causes, and cannot know intent. It is a prioritisation aid for humans, not a prediction, and the README says so.
VERIFIED: 49 tests, 10/10 mutations caught. Every mutation was observed FAILING before the source was restored — a test never seen to fail is a decoration.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function assertValidPeriod(period: PeriodWindow, label: string): void;
export function assertNonOverlapping(current: PeriodWindow, baselinePeriods: PeriodWindow[]): void;
export function countEventsInWindow(events: UsageEvent[], window: PeriodWindow): number;
export function countNegativeSignalsInWindow(events: UsageEvent[], window: PeriodWindow): number;
export function mean(values: number[]): number;
export function tierFor(score: number): ChurnRiskTier;
export function scoreAccountChurnRisk( history: AccountHistory, options: ScoreOptions, ): ChurnRiskResult;
export function naiveChurnAlert(currentCount: number, baselineAvg: number): boolean; export type ChurnRiskTier = "LOW" | "MEDIUM" | "HIGH" | "CRITICAL";
export type SegmentSilenceLabel = "DATA_SILENCE" | "USER_SILENCE" | "INSUFFICIENT_SEGMENT_DATA";01Capabilities
Does
- + SaaS operations
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 49/49 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 13 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 4, 2026 | First public release. |