find-non-lambda-logs
Audits and migrates Log calls in Android, ensuring optimal logging practices and preserving stack traces for better debugging.
Install this skill
or
40/100
Security score
The find-non-lambda-logs skill was audited on May 12, 2026 and we found 6 security issues across 1 threat category, including 3 high-severity. Review the findings below before installing.
Categories Tested
Security Issues
high line 13
Template literal with variable interpolation in command context
SourceSKILL.md
| 13 | 2. **Throwable dropped in catch blocks.** `Log.w/e` calls inside `catch (e: ...)` blocks that interpolate `${e.message}` but don't pass `e` lose the stack trace, and log nothing useful when `e.message |
medium line 25
Template literal with variable interpolation in command context
SourceSKILL.md
| 25 | ```kotlin |
high line 68
Template literal with variable interpolation in command context
SourceSKILL.md
| 68 | Among the Step 2 hits, the calls that interpolate `${e.message}` (or `${t.message}`, `${throwable.message}`) but do not pass the exception itself are a separate bug — they lose the stack trace AND log |
medium line 94
Template literal with variable interpolation in command context
SourceSKILL.md
| 94 | ```kotlin |
high line 104
Template literal with variable interpolation in command context
SourceSKILL.md
| 104 | Switch to `(tag, msg, throwable)` — the lambda overload does **not** accept a throwable, so this case must use the eager-string form. Drop the redundant `${e.message}` from the message text since the |
medium line 106
Template literal with variable interpolation in command context
SourceSKILL.md
| 106 | ```kotlin |
Scanned on May 12, 2026
View Security Dashboard