LookupMark Log Analyzer
v1.1.0Securely analyze system and application logs with automatic sensitive data redaction. Supports OpenClaw gateway logs (journalctl), RAG indexing logs, and que...
⭐ 0· 43·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description claim secure log analysis with redaction; the included script implements that and only targets the declared sources (journalctl unit openclaw-gateway and two local RAG log files). No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md and the script are consistent: they limit reads to ALLOWED_SOURCES and state read-only/no-network. The script does load a user config (~/.config/log-analyzer/config.json) to override error and redact patterns — this can change detection/redaction behavior if the local config is modified. Also user-supplied search regexes are executed locally (could cause expensive regex evaluation).
Install Mechanism
No install spec and only a small Python script are provided, so nothing is downloaded or written to disk by an installer. This is the lowest-risk installation model.
Credentials
The skill requests no environment variables, no credentials, and no special config paths beyond a user-scoped config file for optional pattern overrides. Those config and log paths are proportionate to a log analyzer.
Persistence & Privilege
The skill is not always-enabled and does not modify other skills or system settings. It reads a per-user config file and local logs only; it does not create persistent system-wide privileges.
Assessment
This skill appears to be what it claims: a local, read-only log analyzer with redaction. Before installing or running it, review the included script and be aware of these points: (1) it reads only the journal unit openclaw-gateway and two files under ~/.local/share/local-rag — verify those are the logs you expect; (2) it loads ~/.config/log-analyzer/config.json which can change redaction or error patterns — inspect or create that file if you need stricter redaction; (3) the --search pattern accepts arbitrary regexes from the user — avoid running untrusted or extremely complex regexes (ReDoS); (4) redaction is regex-based and may not catch every secret — do not paste sanitized output into untrusted external services without spot-checking; (5) it invokes journalctl via subprocess (user scope), so ensure you run it as the intended user and not with elevated privileges. If you want extra assurance, run the script locally and inspect its output before granting it any broader automated invocation.Like a lobster shell, security has layers — review code before you run it.
latestvk971s8s979fak79rcbxdw4fzzs847gcc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.