slopguard-cli 0.1.1

CLI tool to catch AI-generated code patterns via static analysis
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

# slopguard-cli

CLI binary for slopguard. Catches AI-generated code patterns and common correctness/security issues via static analysis.

This crate provides the `slopguard` command-line tool. For the core library, see [`slopguard-core`](https://crates.io/crates/slopguard-core). For the full project, see the [main README](https://gitlab.com/ThomasTartrau/slopguard).

## Install

```bash
cargo install slopguard-cli
```

## Commands

| Command | Description |
|---------|-------------|
| `slopguard scan [paths...]` | Scan files for rule violations |
| `slopguard list` | List all active rules |
| `slopguard test` | Validate all rule inline tests (should_match / should_not_match) |
| `slopguard init` | Generate a `slopguard.toml` configuration file |

## Scan Options

| Flag | Description |
|------|-------------|
| `--format <text\|json\|sarif>` | Output format (default: text) |
| `--severity-threshold <error\|warning>` | Minimum severity to report (default: warning) |
| `--config <path>` | Path to a slopguard.toml config file |
| `--no-colors` | Disable colored output |

## Exit Codes

| Code | Meaning |
|------|---------|
| 0 | No findings (or all below severity threshold) |
| 1 | Findings found at or above severity threshold |
| 2 | Configuration error (invalid rule, missing file, bad TOML) |

## Examples

```bash
# Scan the current project
slopguard scan .

# Scan specific directories
slopguard scan src/api/ src/handlers/

# JSON output for CI pipelines
slopguard scan --format json

# SARIF for GitLab/GitHub code scanning integration
slopguard scan --format sarif

# Only fail on errors, not warnings
slopguard scan --severity-threshold error
```

## License

MIT - see [LICENSE](../LICENSE).