JEP Guard intercepts high-risk commands, requires user confirmation, issues temporary tokens, and logs actions with exportable audit receipts.

What to consider before installing: - The package appears to be exactly what it says: a local security/audit daemon that intercepts OpenClaw skill actions and writes audit logs to ~/.jep-guard. Its hooks use a local IPC socket and do not auto-start the daemon — you must start the daemon explicitly. - Review and verify the remaining daemon code (server/router/audit/registry files that were omitted/truncated in the bundle). Those files are responsible for the server-side behavior (network endpoints, any outbound calls, permissions) and are the highest-value review items for security. - Before enabling Full Protection (mode 'full' / manual init): - Inspect daemon/server.js (and router/audit/registry implementations) for any code that performs outbound network calls, binds non-local sockets, or performs privilege escalation. - Check file permissions for ~/.jep-guard (guard.key and audit files) to ensure keys and logs are readable only by the intended user (mode 600/700 used in scripts is appropriate). - When starting the daemon, confirm the IPC socket path ownership/permissions so an attacker cannot create or hijack the socket. Prefer running the daemon as a dedicated, non-root user. - If you want minimal risk initially: install in Passive mode (the installer defaults to it and the post-install script documents that) so you have SDK/logging without interception, and only enable Full mode after code review and manual testing in an isolated environment. - Because some files were truncated in the provided bundle, I recommend either inspecting the full source from the declared repository (https://github.com/hjs-foundation/jep-guard) or running the package in a sandbox/VM and monitoring network and filesystem activity before trusting it in production.

Type: OpenClaw Skill Name: jep-guard Version: 2.0.4 JEP Guard v2.0.4 is a security and auditing framework for the OpenClaw ecosystem that implements the Judgment Event Protocol (JEP). It functions as a 'Causal Operating System' by intercepting skill executions via OpenClaw hooks to provide authorization gating, causal tracing, and reputation scoring. The codebase is professionally structured and demonstrates significant security hardening, such as the complete removal of shell command execution (child_process) in favor of pure Node.js APIs and the requirement for explicit user consent and manual daemon activation. No evidence of data exfiltration, unauthorized persistence, or malicious intent was found; the high-privilege capabilities requested (process control and local networking) are strictly aligned with its stated purpose as a security middleware.