Skip to content

v0.2.0 — richer SARIF field mapping

Choose a tag to compare

View all tags
@Kiransekar Kiransekar released this 10 Jul 18:08
v0.2.0
c93ae4d

SARIF import/export is no longer lossy:

  • Code flows — import parses a qualified engine's codeFlows into an ordered data-flow path (new code_flow column) and surfaces it in the agent fix briefing, so a fixer sees how a defect flows, not just where.
  • Rule relationships — export emits cross-standard equivalences as SARIF reportingDescriptor.relationships (e.g. a MISRA rule linked to its CERT equivalent), with every target resolving to a descriptor.
  • Round-trip — startColumn + codeFlows survive import → export alongside the existing maishac/v1 partialFingerprints identity.

Benchmarked end-to-end (run_sarif_import_test.py, 8/8 checks; see BENCHMARK-SUITE-REPORT.md §4). 33 unit tests green.

Assets 2
Loading