repotoire 0.8.0

Graph-powered code analysis CLI. 110 detectors for security, architecture, bus factor, and code quality.
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

//! Phase 2j annotations entry point — kebab-cased to per-detector intent.
//!
//! The actual parser lives in `super::super::dual_branch_annotation`
//! (consolidated in Phase 2c, after the rule-of-three). This module
//! exists so existing `super::annotation::parse_python_comment` call
//! sites inside the detector keep working without churn, AND so that
//! any Phase 2j-specific annotation kind validation can land here
//! without affecting the shared parser.
//!
//! Phase 2j uses two kinds (per decisions doc D2):
//! - `sql-safe[<reason>]` — collapses to Benign / Info.
//! - `sql-vulnerable[<source>]` — collapses to RealBug at the
//!   existing single-branch severity (typically `Critical` for the
//!   f-string / `.raw()` / `.format()` shapes that the legacy
//!   pattern matcher fires on).
//!
//! The shared parser is kind-agnostic; this module is the natural
//! home for any future Phase 2j-specific kind validation or
//! normalization.

#[allow(unused_imports)]
pub(super) use crate::detectors::security::dual_branch_annotation::{
    parse_python_comment, Annotation,
};