logsentry

• Risk level: Low
• Analyzed: Apr 14, 2026, 9:03 AM
• Findings: 0
• Version: 1.0.0

Overview

The skill's code, install steps, and requested credential (LOGSENTRY_LICENSE_KEY) are consistent with a local log-quality scanner that integrates with git hooks; no unexpected network exfiltration or unrelated credentials are requested.

LogSentry appears to be what it claims: a local, regex-based logging-quality scanner that can integrate with git hooks and uses an optional license key (LOGSENTRY_LICENSE_KEY). Before installing: 1) Review the scripts locally (dispatcher.sh, analyzer.sh, patterns.sh, license.sh) if you can — they run locally and do not send data externally. 2) Be aware that installing hooks will modify your repository's lefthook.yml and will run scans on staged files (you can skip hooks with git commit --no-verify but that bypasses protections). 3) If you don't want the skill to probe your OpenClaw config, do not store a license in ~/.openclaw/openclaw.json or unset LOGSENTRY_LICENSE_KEY; the script will look there for convenience. 4) Ensure you have lefthook installed from a trusted source (brew install lefthook) and that grep, bash, and optional tools (python3/node/jq/openssl) are available if you expect full functionality. 5) If any part of the behavior feels unexpected (automatic repo modification, scanning sensitive files), run the tool in a sandboxed copy of your repository first.