zerum 0.4.0

Deterministic Python code governance: ~75 checks, default/strict profiles, explain mode, optional Ruff orchestration
Documentation 
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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

# Configuration and profiles

Zerum reads `zerum.toml` from the project root (discovered by walking up from the checked path).

## Active profile

```toml
[profile]
name = "default"
```

Built-in profiles:

| Profile | Behavior |
|---------|----------|
| `default` | AST-precise and high-signal rules; noisy pattern heuristics disabled |
| `strict` | All ~75 catalog rules enabled |

Override on the CLI:

```bash
zerum check . --profile strict
```

## Per-check settings

```toml
[checks.ZR001]
enabled = true
max_lines = 80

[checks.ZR401]
severity = "critical"
```

Severity must be one of: `low`, `medium`, `high`, `critical`.

## Profile inheritance

Define layered profiles for teams:

```toml
[profile]
name = "team"

[profiles.base]
extends = "default"

[profiles.base.checks.ZR001]
max_lines = 40

[profiles.team]
extends = "base"

[profiles.team.checks.ZR401]
severity = "high"
```

Top-level `[checks.ZR###]` entries override the active profile chain.

## External checkers

```toml
external_checkers = ["ruff"]
```

Or per invocation:

```bash
zerum check . --with-external ruff
zerum list-checkers
```

External findings use ids like `EXT-RUFF` and `confidence: tool_reported`.

## Schema validation

Invalid check ids (not matching `ZR###`) or unknown severity values fail at config load with a clear error.