python-vibe-guard 0.9.0__tar.gz → 0.11.0__tar.gz

{python_vibe_guard-0.9.0 → python_vibe_guard-0.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-vibe-guard
-Version: 0.9.0
+Version: 0.11.0
 Summary: Runtime anti-pattern scanner for async Python — detects what AI-generated code gets wrong
 License: MIT
 Keywords: async,linter,fastapi,asyncio,static-analysis
@@ -173,6 +173,10 @@ python -m pyvibe src/ --exclude tests
 # Show the research evidence behind a rule (accuracy, false positives, sources)
 python -m pyvibe explain PYVIBE-002
 
+# Baseline mode: suppress pre-existing findings, only fail on new ones
+python -m pyvibe baseline create src/     # snapshot current findings
+python -m pyvibe src/ --baseline          # only reports findings NOT in the baseline
+
 # Exit code: 0 = clean, 1 = violations found, 2 = path error
 ```
 
@@ -255,6 +259,38 @@ python -m pyvibe explain PYVIBE-002
 If a rule has no evidence file, it prints a clear `No evidence file found for PYVIBE-XXX`
 and exits non-zero — it never invents data.
 
+### Baseline mode
+
+Adopting python-vibe-guard on an existing codebase usually means hundreds of pre-existing
+findings you can't fix before CI needs to go green. Baseline mode snapshots the current
+findings once, then only fails on genuinely **new** ones:
+
+```bash
+# Snapshot every current finding into .pyvibe-baseline.json
+python -m pyvibe baseline create src/
+
+# Refuses to run if a baseline already exists — use `update` to overwrite it
+python -m pyvibe baseline update src/
+
+# Full scan, but only reports findings NOT already in the baseline
+python -m pyvibe src/ --baseline
+python -m pyvibe src/ --baseline --json
+python -m pyvibe src/ --baseline --sarif
+
+# `pyvibe scan` is an equivalent, explicit subcommand form of the same flags
+python -m pyvibe scan src/ --baseline
+```
+
+A finding is considered "already known" on an exact match of `(file path, rule ID, line
+number)`. Anything that doesn't match — a new violation, or an existing one that moved to
+a different line — is reported and fails the scan (exit code `1`); an unchanged baseline
+produces exit code `0`.
+
+`.pyvibe-baseline.json` is a plain JSON file — whether to commit it or add it to
+`.gitignore` is up to your team. Commit it if you want the accepted-debt snapshot shared
+and reviewed like any other file; gitignore it if each contributor/CI run should
+regenerate its own baseline instead.
+
 ---
 
 ## CI/CD integration
@@ -352,7 +388,7 @@ python -m pytest tests/ -v
 python tests/test_rules.py
 ```
 
-226 tests: true positives + false-positive guards for every rule, plus SARIF output and `pyvibe explain` coverage.
+268 tests: true positives + false-positive guards for every rule, plus SARIF output, `pyvibe explain`, `pyvibe review`, and baseline mode coverage.
 
 ---
 

{python_vibe_guard-0.9.0 → python_vibe_guard-0.11.0}/README.md

@@ -158,6 +158,10 @@ python -m pyvibe src/ --exclude tests
 # Show the research evidence behind a rule (accuracy, false positives, sources)
 python -m pyvibe explain PYVIBE-002
 
+# Baseline mode: suppress pre-existing findings, only fail on new ones
+python -m pyvibe baseline create src/     # snapshot current findings
+python -m pyvibe src/ --baseline          # only reports findings NOT in the baseline
+
 # Exit code: 0 = clean, 1 = violations found, 2 = path error
 ```
 
@@ -240,6 +244,38 @@ python -m pyvibe explain PYVIBE-002
 If a rule has no evidence file, it prints a clear `No evidence file found for PYVIBE-XXX`
 and exits non-zero — it never invents data.
 
+### Baseline mode
+
+Adopting python-vibe-guard on an existing codebase usually means hundreds of pre-existing
+findings you can't fix before CI needs to go green. Baseline mode snapshots the current
+findings once, then only fails on genuinely **new** ones:
+
+```bash
+# Snapshot every current finding into .pyvibe-baseline.json
+python -m pyvibe baseline create src/
+
+# Refuses to run if a baseline already exists — use `update` to overwrite it
+python -m pyvibe baseline update src/
+
+# Full scan, but only reports findings NOT already in the baseline
+python -m pyvibe src/ --baseline
+python -m pyvibe src/ --baseline --json
+python -m pyvibe src/ --baseline --sarif
+
+# `pyvibe scan` is an equivalent, explicit subcommand form of the same flags
+python -m pyvibe scan src/ --baseline
+```
+
+A finding is considered "already known" on an exact match of `(file path, rule ID, line
+number)`. Anything that doesn't match — a new violation, or an existing one that moved to
+a different line — is reported and fails the scan (exit code `1`); an unchanged baseline
+produces exit code `0`.
+
+`.pyvibe-baseline.json` is a plain JSON file — whether to commit it or add it to
+`.gitignore` is up to your team. Commit it if you want the accepted-debt snapshot shared
+and reviewed like any other file; gitignore it if each contributor/CI run should
+regenerate its own baseline instead.
+
 ---
 
 ## CI/CD integration
@@ -337,7 +373,7 @@ python -m pytest tests/ -v
 python tests/test_rules.py
 ```
 
-226 tests: true positives + false-positive guards for every rule, plus SARIF output and `pyvibe explain` coverage.
+268 tests: true positives + false-positive guards for every rule, plus SARIF output, `pyvibe explain`, `pyvibe review`, and baseline mode coverage.
 
 ---
 

{python_vibe_guard-0.9.0 → python_vibe_guard-0.11.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-vibe-guard"
-version = "0.9.0"
+version = "0.11.0"
 description = "Runtime anti-pattern scanner for async Python — detects what AI-generated code gets wrong"
 readme = "README.md"
 requires-python = ">=3.10"

{python_vibe_guard-0.9.0 → python_vibe_guard-0.11.0}/python_vibe_guard.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-vibe-guard
-Version: 0.9.0
+Version: 0.11.0
 Summary: Runtime anti-pattern scanner for async Python — detects what AI-generated code gets wrong
 License: MIT
 Keywords: async,linter,fastapi,asyncio,static-analysis
@@ -173,6 +173,10 @@ python -m pyvibe src/ --exclude tests
 # Show the research evidence behind a rule (accuracy, false positives, sources)
 python -m pyvibe explain PYVIBE-002
 
+# Baseline mode: suppress pre-existing findings, only fail on new ones
+python -m pyvibe baseline create src/     # snapshot current findings
+python -m pyvibe src/ --baseline          # only reports findings NOT in the baseline
+
 # Exit code: 0 = clean, 1 = violations found, 2 = path error
 ```
 
@@ -255,6 +259,38 @@ python -m pyvibe explain PYVIBE-002
 If a rule has no evidence file, it prints a clear `No evidence file found for PYVIBE-XXX`
 and exits non-zero — it never invents data.
 
+### Baseline mode
+
+Adopting python-vibe-guard on an existing codebase usually means hundreds of pre-existing
+findings you can't fix before CI needs to go green. Baseline mode snapshots the current
+findings once, then only fails on genuinely **new** ones:
+
+```bash
+# Snapshot every current finding into .pyvibe-baseline.json
+python -m pyvibe baseline create src/
+
+# Refuses to run if a baseline already exists — use `update` to overwrite it
+python -m pyvibe baseline update src/
+
+# Full scan, but only reports findings NOT already in the baseline
+python -m pyvibe src/ --baseline
+python -m pyvibe src/ --baseline --json
+python -m pyvibe src/ --baseline --sarif
+
+# `pyvibe scan` is an equivalent, explicit subcommand form of the same flags
+python -m pyvibe scan src/ --baseline
+```
+
+A finding is considered "already known" on an exact match of `(file path, rule ID, line
+number)`. Anything that doesn't match — a new violation, or an existing one that moved to
+a different line — is reported and fails the scan (exit code `1`); an unchanged baseline
+produces exit code `0`.
+
+`.pyvibe-baseline.json` is a plain JSON file — whether to commit it or add it to
+`.gitignore` is up to your team. Commit it if you want the accepted-debt snapshot shared
+and reviewed like any other file; gitignore it if each contributor/CI run should
+regenerate its own baseline instead.
+
 ---
 
 ## CI/CD integration
@@ -352,7 +388,7 @@ python -m pytest tests/ -v
 python tests/test_rules.py
 ```
 
-226 tests: true positives + false-positive guards for every rule, plus SARIF output and `pyvibe explain` coverage.
+268 tests: true positives + false-positive guards for every rule, plus SARIF output, `pyvibe explain`, `pyvibe review`, and baseline mode coverage.
 
 ---
 

{python_vibe_guard-0.9.0 → python_vibe_guard-0.11.0}/python_vibe_guard.egg-info/SOURCES.txt

@@ -9,7 +9,9 @@ pyvibe/__init__.py
 pyvibe/__main__.py
 pyvibe/analyzer.py
 pyvibe/autofix.py
+pyvibe/baseline.py
 pyvibe/cli.py
+pyvibe/diff.py
 pyvibe/explain.py
 pyvibe/rule_docs.py
 pyvibe/sarif.py
@@ -35,6 +37,8 @@ pyvibe/rules/sqlite_async.py
 pyvibe/rules/subprocess_async.py
 pyvibe/rules/threading_lock.py
 pyvibe/rules/while_true_no_await.py
+tests/test_baseline.py
+tests/test_diff.py
 tests/test_exclude.py
 tests/test_explain.py
 tests/test_rules.py

python_vibe_guard-0.11.0/pyvibe/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.11.0"

{python_vibe_guard-0.9.0 → python_vibe_guard-0.11.0}/pyvibe/analyzer.py

@@ -1,6 +1,6 @@
 import ast
 from pathlib import Path
-from typing import FrozenSet, List
+from typing import FrozenSet, List, Optional
 
 from pyvibe.rules.base import Violation
 from pyvibe.rules.async_sleep import AsyncSleepRule
@@ -132,9 +132,16 @@ def analyze_file(
     path: Path,
     *,
     downgrade_in_tests: FrozenSet[str] = TEST_FILE_DOWNGRADE,
+    line_filter: Optional[FrozenSet[int]] = None,
 ) -> List[Violation]:
+    """line_filter: if given, only violations whose `line` is in this set
+    are returned (used by `pyvibe review` to report only diff-touched lines).
+    """
     source = path.read_text(encoding="utf-8", errors="ignore")
-    return analyze_source(source, filepath=str(path), downgrade_in_tests=downgrade_in_tests)
+    violations = analyze_source(source, filepath=str(path), downgrade_in_tests=downgrade_in_tests)
+    if line_filter is not None:
+        violations = [v for v in violations if v.line in line_filter]
+    return violations
 
 
 DEFAULT_EXCLUDES = frozenset({

python_vibe_guard-0.11.0/pyvibe/baseline.py

@@ -0,0 +1,73 @@
+"""Baseline support — `pyvibe baseline create/update` and `pyvibe scan --baseline`.
+
+A baseline is a snapshot of existing findings ({filepath: [{rule_id, line,
+message}, ...]}) that a team can choose to commit or gitignore (see README).
+Once created, `pyvibe scan --baseline` only reports genuinely NEW
+violations — anything already in the baseline is suppressed — so a
+codebase can adopt python-vibe-guard incrementally instead of having to
+fix every existing hit before CI goes green.
+"""
+import json
+from pathlib import Path
+from typing import Dict, Set, Tuple
+
+DEFAULT_BASELINE_PATH = ".pyvibe-baseline.json"
+
+
+class BaselineNotFoundError(Exception):
+    """Raised when `pyvibe scan --baseline` can't find/parse the baseline file."""
+
+
+def build_baseline(file_results: Dict) -> dict:
+    """file_results: {path: [Violation, ...]} as produced by analyze_file /
+    analyze_directory. Returns the JSON-serializable baseline:
+    {filepath: [{rule_id, line, message}, ...]}.
+    """
+    return {
+        str(path): [
+            {"rule_id": v.rule_id, "line": v.line, "message": v.message}
+            for v in violations
+        ]
+        for path, violations in file_results.items()
+    }
+
+
+def write_baseline(file_results: Dict, output_path=DEFAULT_BASELINE_PATH) -> None:
+    baseline = build_baseline(file_results)
+    Path(output_path).write_text(json.dumps(baseline, indent=2), encoding="utf-8")
+
+
+def load_baseline(path=DEFAULT_BASELINE_PATH) -> dict:
+    baseline_path = Path(path)
+    if not baseline_path.exists():
+        raise BaselineNotFoundError(
+            f"No baseline found at {path}. Run `pyvibe baseline create` first."
+        )
+    try:
+        return json.loads(baseline_path.read_text(encoding="utf-8"))
+    except json.JSONDecodeError as e:
+        raise BaselineNotFoundError(f"Baseline at {path} is not valid JSON: {e}") from e
+
+
+def _baseline_keys(baseline: dict) -> Set[Tuple[str, str, int]]:
+    """Flatten the baseline into (filepath, rule_id, line) triples for exact,
+    O(1) membership checks.
+    """
+    return {
+        (filepath, entry["rule_id"], entry["line"])
+        for filepath, entries in baseline.items()
+        for entry in entries
+    }
+
+
+def filter_new_violations(file_results: Dict, baseline: dict) -> Dict:
+    """Return only the violations in file_results NOT present in baseline,
+    matched exactly on (filepath, rule_id, line).
+    """
+    known = _baseline_keys(baseline)
+    new_results = {}
+    for path, violations in file_results.items():
+        new = [v for v in violations if (str(path), v.rule_id, v.line) not in known]
+        if new:
+            new_results[path] = new
+    return new_results