sarif-parsing

Name: sarif-parsing
Availability: InStock
Author: metallegbob

Parse SARIF files to extract and normalize findings for cross-tool analysis.

11|13|Updated Mar 25, 2026

Search Tags:#security #reporting #deduplication #parsing #static-analysis #ci-cd #sarif

Ready to run

npx skills add https://github.com/MetalLegBob/drfraudsworth --skill sarif-parsing-metallegbob

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sarif-parsing
Source: https://github.com/MetalLegBob/drfraudsworth/tree/main/.claude/skills/sarif-parsing
Command: npx skills add https://github.com/MetalLegBob/drfraudsworth --skill sarif-parsing-metallegbob

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest, normalize, and analyze SARIF outputs from multiple static analysis tools to provide a unified view of findings, enabling deduplication, cross-run correlation, and CI/CD reporting.

Core Features & Use Cases

Ingest SARIF files from diverse analyzers and normalize their structures for consistent analysis.
Deduplicate findings across runs using fingerprints to track issues over time.
Aggregate and summarize results by file, rule, and severity for dashboards and reports.
Use Case: Consolidate security findings from multiple scanners into a single, actionable SARIF view for faster remediation.

Quick Start

Analyze a SARIF file such as results.sarif to generate an integrated findings summary.

Frequently Asked Questions about sarif-parsing

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

FAQPage Schema

How do I consolidate SARIF files from multiple static analysis tools into a single report?▼

Consolidate SARIF files by parsing and normalizing findings from diverse analyzers to provide a unified view. This consolidation enables cross-run correlation, deduplication using fingerprints, and summarized reporting by file, rule, and severity.

Can I deduplicate static analysis findings across multiple CI/CD runs?▼

Yes, deduplicate static analysis findings across multiple CI/CD runs by applying fingerprinting logic to normalized SARIF data. This cross-run correlation tracks recurring issues over time, ensuring consistent deduplication and actionable remediation.

What is the best way to parse large SARIF datasets in CI pipelines?▼

Parse large SARIF datasets in CI pipelines using defensive parsing and optional streaming techniques. This approach handles optional fields, applies path normalization, and aggregates results by rule and severity without failing on malformed data.

Does SARIF parsing handle missing optional fields and path normalization?▼

Yes, SARIF parsing handles missing optional fields and path normalization through defensive parsing logic. It safely extracts findings, normalizes file paths, and generates fingerprints for aggregation even when optional SARIF schema fields are absent.

How do I aggregate security findings by rule and severity for dashboards?▼

Aggregate security findings by rule and severity by parsing SARIF outputs to extract and normalize findings. This process summarizes deduplicated results, providing an integrated view of static analysis data suitable for dashboards and CI/CD reporting.

Why do I need to normalize SARIF results for cross-tool analysis?▼

You need to normalize SARIF results for cross-tool analysis because diverse static analyzers output varying structures. Normalizing these structures ensures consistent deduplication, accurate fingerprinting, and reliable aggregation by file, rule, and severity.