Sobelow security-focused static analysis for Phoenix and Elixir projects
- GitHub stars
- 176
Install
/plugin install sobelow@elixirRun it inside Claude Code after adding the marketplace with /plugin marketplace add bradleygolden/claude-marketplace-elixir.
Contents
Discovered from sourceAgents 2
Changelog
All notable changes to this plugin will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]
[1.2.1] - 2025-01-08
Changelog tracking begins with this version. For prior history, see git log.
Sobelow Security Analysis Plugin
Security-focused static analysis for Phoenix and Elixir projects using Sobelow.
Overview
This plugin integrates Sobelow security scanning into your Claude Code workflow, providing automated security analysis for Phoenix and Elixir applications. Sobelow identifies potential security vulnerabilities including XSS, SQL injection, command injection, insecure configuration, and more.
Features
- Post-edit security scanning: Automatically analyzes files after edits to identify security issues
- Pre-commit validation: Blocks commits that introduce medium or high confidence security vulnerabilities
- Skip file support: Respects
.sobelow-skipsfile for managing false positives - Inline comment support: Honors
# sobelow_skipcomments for function-level suppressions - Intelligent filtering: Only runs on Elixir projects with Sobelow dependency
- Confidence-based blocking: Blocks commits on medium and high confidence findings, allowing low confidence issues to pass
Installation
/plugin marketplace add github:bradleygolden/claude-marketplace-elixir
/plugin install sobelow@elixir
Requirements
Your Elixir project must have Sobelow as a dependency:
# mix.exs
def deps do
[
{:sobelow, "~> 0.14", only: [:dev, :test], runtime: false}
]
end
Then run:
mix deps.get
How It Works
Post-Edit Security Scan
After editing .ex or .exs files, the plugin automatically:
- Detects the Mix project root
- Checks if Sobelow is a project dependency
- Runs
mix sobelow --format json --skip(respects your skip configuration) - Provides security findings to Claude as context
- Suggests fixes or skip options for false positives
Pre-Commit Validation
Before git commit commands, the plugin:
- Runs
mix sobelow --skip(respects your skip configuration) - Blocks the commit if any security findings are reported
- Users control what gets reported via
.sobelow-conf(threshold, ignore types, etc.) - Provides clear guidance on fixing or suppressing findings
Default behavior: Blocks on any findings. Use .sobelow-conf to customize (e.g., --threshold medium to only report medium/high confidence issues).
Note: Skips if project has a precommit alias (defers to precommit plugin)
Managing False Positives
Sobelow provides multiple ways to handle false positives:
1. Inline Comments (Function-level)
Add a comment before the function:
# sobelow_skip ["SQL.Query", "XSS.Raw"]
def safe_function(params) do
# Actually safe code that Sobelow flags
end
2. Mark All Current Findings
# In your project directory
mix sobelow --mark-skip-all
This adds all current findings to .sobelow-skips file as MD5 hashes.
3. Selective Marking (Recommended)
When you have mixed results (some real issues, some false positives):
# Mark only specific types as false positives
# Ignore the REAL issues first, then mark the rest
mix sobelow --ignore XSS.Raw,Config.HTTPS --mark-skip-all
This workflow:
- Shows all findings
- Ignores the real issues you want to fix (XSS.Raw, Config.HTTPS)
- Marks only the remaining findings (false positives) in
.sobelow-skips - Next run with
--skipwill only show the real issues
4. Configuration File
Create .sobelow-conf for persistent options:
mix sobelow --exit Low --verbose --save-config
The plugin automatically picks up this configuration. CLI options override config file settings.
Understanding Skip Behavior
The plugin always runs with --skip to respect your skip decisions:
- Inline comments (
# sobelow_skip): Automatically honored - Skip file (
.sobelow-skips): Automatically used if present - Configuration (
.sobelow-conf): Automatically loaded
This ensures you only see new or unfixed security findings, not known false positives.
Workflow Example
# 1. Edit a file - Sobelow runs and finds issues
# Claude shows: "Sobelow found SQL.Query and XSS.Raw issues"
# 2. Review findings
# - SQL.Query: False positive (using parameterized query correctly)
# - XSS.Raw: Real issue (needs fixing)
# 3. Mark the false positive
mix sobelow --ignore XSS.Raw --mark-skip-all
# 4. Fix the real issue with Claude's help
# Claude helps refactor the XSS.Raw vulnerability
# 5. Commit - pre-commit hook runs
git commit -m "fix: resolve XSS vulnerability"
# ✅ Passes (SQL.Query skipped, XSS.Raw fixed)
Hook Configuration
PostToolUse Hook
- Trigger: After Edit, Write, or MultiEdit tools
- Timeout: 30 seconds
- Behavior: Non-blocking (always allows the edit)
- Output: Provides findings as
additionalContextto Claude
PreToolUse Hook
- Trigger: Before Bash tool (git commit commands)
- Timeout: 30 seconds
- Behavior: Blocking (JSON permissionDecision: "deny" prevents commit)
- Threshold: Medium and High confidence findings
Customization
Adjust Exit Threshold
Edit your .sobelow-conf or run:
# Block only on high confidence findings
mix sobelow --exit High --save-config
# Block on all findings (including low confidence)
mix sobelow --exit Low --save-config
Ignore Specific Finding Types
# Permanently ignore certain types
mix sobelow --ignore Config.HTTPS,Traversal --save-config
Verbose Output
# Show code snippets in findings
mix sobelow --verbose --save-config
Troubleshooting
Hook doesn't run
Check if Sobelow is in dependencies:
grep sobelow mix.exs
If missing, add it:
{:sobelow, "~> 0.14", only: [:dev, :test], runtime: false}
Too many false positives
Use the selective marking workflow:
# Review findings, then mark specific types as skips
mix sobelow --ignore RealIssue1,RealIssue2 --mark-skip-all
Want to re-scan previously skipped findings
# Clear all skips
mix sobelow --clear-skip
# Or manually delete the skip file
rm .sobelow-skips
Pre-commit blocking on low confidence findings
The plugin uses --exit Medium by default. To adjust:
# Only block on high confidence
mix sobelow --exit High --save-config
Or edit the pre-commit script at plugins/sobelow/scripts/pre-commit-check.sh.
Security Best Practices
- Fix real issues first: Don't skip findings without review
- Use selective marking:
--ignore Real1,Real2 --mark-skip-allprevents hiding real issues - Regular re-scans: Periodically run
mix sobelow --clear-skipto verify old skips - Code review: Have security findings reviewed by team members
- CI/CD integration: Consider running Sobelow in CI with
--exit High
Learn More
Changelog
See CHANGELOG.md for version history.
License
MIT
Hooks 2
Sponsors
Details
- Marketplace
- bradleygolden/claude-marketplace-elixir
- Source
- plugins/sobelow
- Category
- Community
- License
- MIT
- Keywords
- elixir, phoenix, sobelow, security, static-analysis, vulnerability-scanning
