clawhub:jep-guard-clawhub@1.2.0
ClawHub · checked 19 Oct 2026, 15:03 UTC · checker 2026-10-19.2 · log index 123
Record issued 19 Oct 2026
Issued 19 Oct 2026, 15:03 UTC · clawhub:jep-guard-clawhub@1.2.0
nothing runs
Nothing of this package's own runs at install.
Nothing of this package's own runs when it is installed. Loading it as OpenClaw does, with register() called and decoy OpenClaw keys in its config and in ~/.openclaw, touched nothing we watch either. Its tools, hooks and services were not called, so what they do when an agent uses them is not covered.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
The install steps section lists what would have run: nothing. A dependency may still run something; see Dependencies.
ClawHub release
- Plugin
- jep-guard-clawhub@1.2.0
- SHA-256
- bdda62daebb58ee6211e34bc21e71de06e780a5c83b3939372d34fde4350da5e
The bytes checked had the SHA-256 ClawHub publishes for this release, or nothing would have run. OpenClaw installs plugins with npm --ignore-scripts, so no install step of the plugin or of its dependencies runs on the host, and none was run here.
Install steps
clawhub:jep-guard-clawhub has no install step of its own.
No dependency runs anything at install.
What the run reached
Nothing was observed for this run.
First import
It was loaded as OpenClaw loads a plugin: ./openclaw.js imported, OpenClaw's own modules stood in for, and register() called with a stand-in OpenClaw API whose config holds decoy gateway and bot tokens. It exited 0.
What register() asked the API for, as printed from inside the plugin's own process. That is the plugin's account, shown for reading, not part of the signed evidence:
- openclaw entry ./openclaw.js: register(api) called; it asked the API for: registerTool(jep_guard_health)
Loading it and its register() reached nothing we watch.
- Programs
- node
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
The tools, hooks and services register() hands to OpenClaw were not called, so what they do when an agent uses them is not covered.
Dependencies
0 of 0 installed, as npm would on linux x64 musl.
it declares no dependencies beyond openclaw, which the host provides
Since the previous version
No comparison with an earlier version was made for this check.
Sandbox
network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user
Signature and transparency log
- level
- nothing_runs
- verdict
- manual_review
- reasonCode
- no_install_steps
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-19T15:03:48Z
- contentSha256
- bdda62daebb58ee6211e34bc21e71de06e780a5c83b3939372d34fde4350da5e
- contentSizeBytes
- 45398 (44 KB)
- log index
- 123
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 19 Oct 2026, 15:03 UTC
What this does and does not say
The claim is about the bytes, not the name.
The signature covers this exact ClawHub release. Another version is another check.
A quiet trace is evidence, not proof.
We traced loading the plugin. Its tools were not called, so what they do later is out of reach.
A signature is not an endorsement.
It says what happened, not that the code is good.
Twenty checks an hour for each network address. When a limit is ours, the record says unfinished and names it.