sarif-parsing

Parse SARIF 2.1.0 logs to extract and deduplicate security findings.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill sarif-parsing-balic-ai-ml-r-d-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sarif-parsing
Source: https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents/tree/main/packages/skills/skills/static-analysis/skills/sarif-parsing
Command: npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill sarif-parsing-balic-ai-ml-r-d-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SARIF parsing and analysis to turn static-analysis results into a clean, deduplicated dataset that is easy to query and report.

Core Features & Use Cases

  • Deduplicate findings across runs using stable fingerprints to track regressions.
  • Aggregate results from multiple tools for CI/CD dashboards and risk reporting.
  • Extract structured fields (rule IDs, severities, file paths, and messages) for downstream analytics and alerts.

Quick Start

Parse results.sarif and generate a deduplicated summary of findings.

Frequently Asked Questions about sarif-parsing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse SARIF files to deduplicate static analysis findings?

To parse SARIF files and deduplicate static analysis findings, extract structured fields like rule IDs and severities, applying stable fingerprinting and path normalization to track regressions across multiple CI/CD runs.

What is stable fingerprinting in SARIF results processing?

Stable fingerprinting in SARIF processing is the mechanism used to uniquely identify and deduplicate security findings across multiple static analysis runs, enabling accurate regression tracking and clean CI/CD reporting.

Can I aggregate SARIF logs from multiple static analysis tools for CI/CD dashboards?

Yes, you can aggregate SARIF 2.1.0 logs from multiple static analysis tools. This skill processes combined results to extract rule IDs, severities, and file paths, generating deduplicated datasets for CI/CD risk reporting.

What's the best way to extract rule IDs and severities from SARIF for downstream analytics?

The best way to extract rule IDs and severities from SARIF for analytics is using the provided Python and jq-based workflow templates, which parse the SARIF structure and output clean, structured data for alerts and dashboards.

What are common pitfalls when normalizing file paths in SARIF logs?

Common pitfalls when normalizing file paths in SARIF logs include inconsistent path formatting across different static analysis tools, which can cause deduplication failures and inaccurate regression tracking if not properly standardized.