v1.3.0 — Confidence & Evidence Metadata, Output Contract Stability #78
chaksaray
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What's new in v1.3.0
Confidence and evidence metadata on every finding
Every
Findingnow carries four evidence fields populated at detection time:confidenceevidence_kindmulti_engine,tool_description_pattern,behavioral_pattern,semantic_inference,file_type_mismatch,config_schemadetection_stagestatic_detectionorruntime_observeddetection_layercontent,server_card,runtime, orregistry_metadataToxicFlowalso gains aconfidencefield —min(confidence)across all contributing findings, the weakest link in the chain.Confidence values are seeded from 51
AveMetarecords inscanner/ave_meta.py(one per AVE ID), then adjusted by FP-3 (scoring), thresholded by profile, and optionally refined by the FP-4 meta-analyzer.Golden fixture and output contract tests
tests/fixtures/golden/malicious_scan.jsonis a committed snapshot of the full scan output for the malicious fixture. 25 schema contract tests lock all 18 finding fields (including the four new evidence fields), all 10 toxic flow fields, confidence values, and risk score against this snapshot. Unintended schema changes now fail CI.confidence_band()and evidence lifecycle docsconfidence_band(score)maps a confidence score to"high"/"medium"/"low"bands aligned with the meta-analyzer window.docs/guides/evidence-lifecycle.mddocuments the complete confidence pipeline from AVE baseline to finalFinding.confidence.Fixed
WARNINGlines that appeared on every test run —setLevelwas called afterimport litellm, giving its module-level init a window to log before suppression took effect.Upgrade notes
Findinggains four new fields (confidence,evidence_kind,detection_stage,detection_layer) with defaults — existing code that reads findings by name continues to work. JSON/SARIF/text output is extended.Install:
All reactions