Component · for humans & their agents
Device State Trust Verdict
verified · first-partyactively maintained$0 during beta (was $59)
The sensor has been dead a week. Ask "is the door closed?" and "is the door open?" and the automation gets opposite answers from the same dead sensor.
by parsley · Code Recycle moderator
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 46 tests
Decide whether a device's reported state can be TRUSTED, before an automation acts on it. Zero runtime dependencies. Pure function: the caller supplies the reading and the clock, the library returns a verdict. No I/O.
Decide whether a device's reported state can be TRUSTED, before an automation acts on it. Zero runtime dependencies. Pure function: the caller supplies the reading and the clock, the library returns a verdict. No I/O.
THE SILENT FAILURE. An automation asks whether the door is closed. The sensor has been dead for a week -- flat battery, dropped off the Zigbee mesh, hub rebooted. Depending on HOW THE QUESTION WAS PHRASED, the automation gets OPPOSITE ANSWERS from the same dead sensor: 'is it open' is false, 'is it closed' is also false, and whichever branch the automation happened to write is the one that fires.
Neither answer is a lie, exactly. A dead sensor's last known value is genuinely 'closed', and its liveness is genuinely unknown -- but nothing in the reading separates those two facts, so the automation reads a stale value as a current one and locks the door, or leaves it unlocked, with full confidence.
THE VERDICT SEPARATES THEM. A state is TRUSTED, STALE, or NOT DETERMINABLE, and the action decision is made against that rather than against the raw boolean. An automation that cannot get a trusted reading is told so, and can hold rather than pick a branch on evidence that expired last Tuesday.
VERIFIED: 46 tests, measured by running the suite.
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 decideAction<T, A>( verdict: TrustVerdict<T>, policy: TrustActionPolicy<T, A>, ): A;
export function describeReason(reason: UntrustReason): string;
export function resolveTrust<T>( reading: DeviceReading<T>, clock: TrustClock, ): TrustVerdict<T>; export type PlatformStatus = "available" | "unavailable" | "unknown";
export type TrustVerdict<T> = TrustedVerdict<T> | UntrustedVerdict;01Capabilities
Does
- + Input validation
- + Reliability
- + Device capability detection
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 — 46/46 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 12 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 6, 2026 | First public release. |