thingctx@0.2.2
CAUTION· install onlyPublisher claims: "Drive any agent against any W3C WoT Thing, over any transport. No per-integration server." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 58 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
THINGCTX_MLOCK_SECRETSTHINGCTX_REQUIRE_AUTHor--client-secrets-file/--client-secretConfiguration, not credentials: THINGCTX_APPROVE_WHEN, THINGCTX_BLOCK_PRIVATE, THINGCTX_DOWNLOAD_DIR, THINGCTX_FS_MAX_BYTES, THINGCTX_FS_ROOT, THINGCTX_IDENTITY, THINGCTX_MAX_CHAIN_HOPS, THINGCTX_MAX_DOWNLOAD_BYTES, THINGCTX_MAX_TD_BYTES, THINGCTX_MODEL, THINGCTX_POLICY, THINGCTX_REGISTRY, THINGCTX_TOOL_MODE, THINGCTX_VERBOSE- Where it talks to
- no vendor host named in the codeAlso device.local, thingctx.dev, microsoftonline.com, microsoft.com, cloudflareaccess.com, windows.net, hub.local, thingctx.invalid — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names device.local, thingctx.dev, microsoftonline.com, microsoft.com, cloudflareaccess.com, windows.net, hub.local, thingctx.invalid as well as its own vendor. The guard injects THINGCTX_MLOCK_SECRETS, THINGCTX_REQUIRE_AUTH only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-17 and scored it 60/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Credential pass-through configuration; Collects secret-named environment variables and sends data out. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
"""Pass through credential material the caller already built.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if importlib.util.find_spec("paho") is not None:Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.for key, val in os.environ.items():Fix: Never read or enumerate credential locations; accept a documented environment variable instead.if importlib.util.find_spec("httpx") is not None:Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.if importlib.util.find_spec("av") is not None:Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for thingctx@0.2.2 as of 6 min ago. This is the package itself, not its dependencies.
What would make this Verified
20 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Collects secret-named environment variables and sends data out≈ +9 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
- Unclaimed publisher≈ +8 on the totalClaim thingctx: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Dynamic module loading≈ +1 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.