Skip to converter

SARIF 2.1.0 lint findings (restricted) to CSV Converter.

Exchange supported lint-report findings between SARIF 2.1.0 lint findings (restricted) and CSV locally on your device.

Featured resources

App or project

NGSpeak: Language Learning App

Learn English and Bengali with 160 offline-first lessons across CEFR A1–C2, including speaking, writing, pronunciation practice, and progress tracking.

Download Now

Convert your file

INPUTSARIF 2.1.0 lint findings (restricted)
OUTPUTCSV
Files stay on your device

Up to 2 MiB · 1–5,000 simple lint findings · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert SARIF 2.1.0 lint findings (restricted) to CSV

  1. Choose a source file. Select a real SARIF 2.1.0 lint findings (restricted) file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated CSV file. Your original file is unchanged.

FORMAT GUIDE

Why convert SARIF 2.1.0 lint findings (restricted) to CSV?

Inspect portable rule, severity and source-location findings in a spreadsheet or transfer the supported diagnostic subset to another reporting format.

  • Reviewing actionable code-quality warnings in a spreadsheet.
  • Converting a curated ESLint JSON diagnostic report into basic SARIF findings.
  • Creating simplified ESLint-compatible diagnostic records from a reviewed CSV table.

UNDERSTAND YOUR FILES

SARIF 2.1.0 lint findings (restricted) vs. CSV: what changes?

Input · SARIF 2.1.0 lint findings (restricted)

SARIF 2.1.0 is a standardized static-analysis report format. This tool handles only the documented, canonical NGInfinite six-field interchange profile, not arbitrary SARIF reports.

Output · CSV

Comma-separated tabular text; quotation marks may enclose commas and line breaks within fields.

Inspect portable rule, severity and source-location findings in a spreadsheet or transfer the supported diagnostic subset to another reporting format. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Before you share the output

Check column headings, escaped characters, delimiters and empty values. Data type information and spreadsheet formulas may not survive a plain-text format change.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

Supports 1–5,000 simple static-analysis findings across at most 500 relative POSIX source paths in a 2 MiB UTF-8 JSON file. Structured data requires exactly six columns, in order: file, rule_id, severity, line, column, message. Files must be grouped consecutively, severity must be error or warning, lines and columns positive, rule IDs portable, and messages plain single-line text. The ESLint JSON source accepts only message ruleId, severity (1/2), message, line and column, plus accurate aggregate counts or empty ancillary metadata. Existing fixes, suggestions, end positions, message IDs, source snippets, suppression records, fatal parse errors and custom metadata are rejected. SARIF 2.1.0 accepts only a single canonical NGInfinite Lint Interchange tool run, with one basic physical location per finding; noncanonical tool runs, extended rule metadata, code flows, fingerprints, fixes, other severity levels and URI bases are rejected. Arbitrary third-party SARIF exports and ordinary ESLint outputs with rich metadata may require simplification first. Source files are not read, scripts are never executed and reports stay in your browser. Keep originals and verify imported results.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

SARIF 2.1.0 lint findings (restricted) to CSV questions

Does this run a code scanner or execute source code?

No. It converts existing report data locally without opening the referenced source files.

Which table headings are required?

Exactly: file, rule_id, severity, line, column, message.

Can it convert full ESLint or SARIF diagnostics?

No. Complex metadata, fixes and other unsupported report features are rejected to avoid silent data loss.