v0.5.0
2026-02-27
ПОСЛЕДНЕЕ
AI Triage 2-Pass Engine (Major)
-
Two-pass AI triage pipelineintroduced a dedicated
Pass Acandidate phase andPass Breviewer phase for false-positive reduction with explicitkeep/dropreasoning. -
Family-aware triage routingfindings are grouped into security families (
sql_nosql_injection,xss_template,command_exec,auth_access,crypto_secrets,path_file,deserialization_ssrf_xxe,misc) before model evaluation. -
Structured schema validation for model outputtriage responses are normalized and validated to guarantee stable
id/decision/reasoncontracts. -
Fail-safe behaviorwhen triage cannot issue a reliable decision (provider issues, invalid payloads, timeouts), findings default to
keep.
Triage Decision Quality & Safety
-
LLM-first final decisioningtriage no longer performs forced heuristic
dropactions in the AI stage; heuristics are now used as contextual hints only. -
High-severity guardrails
CRITICAL(andHIGHoutside generated assets) remain protected from aggressive dropping. -
Risk-language guardraildrop reasons that indicate explicit exploitability/risk are automatically converted to
keepfor analyst safety. - Improved reason quality policyprompts now enforce concrete evidence-based rationale format with local anchors from snippet/context.
-
Consistency metricsadded and stabilized triage counters (
passADropCandidates,passBDropConfirmed,passBVetoedToKeep,forcedDrops) for clear runtime diagnostics.
Project Context Intelligence (Framework-Agnostic)
- Project mitigation context indexingtriage now scans the repository for local security helper definitions and injects relevant related definitions per finding.
- Broader language/template support in context extractionexpanded source/template recognition to better cover mixed modern stacks and heterogeneous codebases.
- Safer route-helper inferenceroute helper shortcuts are now constrained by framework context to reduce framework-specific false assumptions.
Streaming AI Pipeline (Latency & Cost)
- Streaming orchestration addedenrichment starts as soon as triage emits kept batches, without waiting for full triage completion.
- Code pipeline decouplingtriage and enrichment now operate as separate services with controlled concurrency and deterministic ordering.
-
Selective enrichmentonly
keepfindings proceed to AI enrichment, reducing unnecessary token usage and end-to-end latency.
Sidebar & Settings UX
-
New triage strategy setting in sidebarusers can select
conservative,balanced, oraggressivedirectly in configuration UI. - Persistent strategy preferencetriage strategy selection is now persisted globally across sessions/workspaces.
- Status messaging updatesscan lifecycle now explicitly reports triage phase and AI pipeline progression.
Scan/Schema Hardening
- Default exclusions tightenedimproved workspace scan noise filtering for generated/minified assets and bulky frontend artifact paths.
- Built-in excludes always enforceduser-defined excludes now extend defaults rather than replacing them.
-
Enrichment schema resiliencenormalized AI payload edge cases (e.g.,
impactarrays, unknowncomplexityvalues) to avoid enrichment failures. - Cache version bumpsenrichment and triage persistent cache keys were updated to ensure clean rollout of new behavior.
Test Coverage & Documentation
- New triage unit suitesadded dedicated tests for family routing, prefiltering, streaming triage/enrichment pipeline, guardrails, and stats consistency.
- Architecture docs for triage flowadded internal design reference for the two-pass AI triage model.