sarif parsing

Other Community

Skill notes

When to Use

Use this skill when: Reading or interpreting static analysis scan results in SARIF format Aggregating findings from multiple security tools Deduplicating or filtering security alerts Extracting specific vulnerabilities from SARIF files

When NOT to Use

Do NOT use this skill for: Running static analysis scans (use CodeQL or Semgrep skills instead) Writing CodeQL or Semgrep rules (use their respective skills) Analyzing source code directly (SARIF is for processing existing scan results) Triaging findings without SARIF input (use variant-analysis or audit skills)

SARIF Structure Overview

SARIF 2.1.0 is the current OASIS standard. Every SARIF file has this hierarchical structure:

Severity Is Not Always on the Result

result.level is optional. CodeQL omits it on every result and records severity on the rule as defaultConfiguration.level, which the result inherits. Read result.level directly and a CodeQL run scores as clean however many errors it found, which is how a severity gate ends up exiting 0 on a failing repo. Resolve severity in this order (SARIF 2.1.0 section 3.27.10):

Why Fingerprinting Matters

Without stable fingerprints, you can't track findings across runs: Baseline comparison: "Is this a new finding or did we see it before?" Regression detection: "Did this PR introduce new vulnerabilities?" Suppression: "Ignore this known false positive in future runs" Tools report different paths (/path/to/project/ vs /github/workspace/), so path-based matching fails. Fingerprints hash the content (code snippet, rule ID, relative location) to create stable identifiers regardless of environment.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview sarif-parsing.preview
# Severity Is Not Always on the Result

1. `kind` other than `"fail"` (a pass/notApplicable record), so `"none"`
2. `result.level`, when present
3. the matched rule's `defaultConfiguration.level`, joining `ruleIndex` into
4. `"warning"`, the SARIF default

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.