A tool in the ImagineQira ecosystem / Source-backed clarity01 — GITHUB WORKFLOW INTELLIGENCE

QIRA PROOF / FREE WORKFLOW CHECK

Check one workflow.
See what needs review.

Paste GitHub Actions YAML, inspect actual matching lines, and export a checklist. No account, no charge, no GitHub permissions.

1 / Add a workflow2 / Review the observations3 / Decide whether you need a full assessment

Everything runs in your browser. Qira does not receive your YAML. Never paste secrets or access tokens.

STEP 1 / PASTE OR OPEN

One workflow YAML file

One file only, up to 32 KB and 450 lines. This is a narrow configuration-pattern check.

Where do I find a workflow file?
  1. Open a GitHub repository you own or are authorized to inspect.
  2. Go to the .github/workflows/ folder and open one .yml or .yaml file.
  3. Copy the workflow YAML into the box, or download that file and choose it below.

Do not paste secrets, access tokens or unrelated private source. This free checker never contacts GitHub or uploads the file.

What does the free checker examine?

It looks for nine limited configuration-pattern categories: mutable action references; write-all and individual token write scopes; OIDC token permissions; pull_request_target triggers; shell interpolation of event input or secrets; SSH host-key collection; and explicitly persisted checkout credentials.

These are review prompts, not confirmed vulnerabilities. This tool does not fully parse YAML, follow reusable workflows, inspect repository policies, or execute anything. For more comprehensive free automated analysis, consider zizmor or GitHub's official security guidance.

0 / 32,000
No email gate or server upload

Want to try a remediation? Edit the YAML above and run the check again. The comparison will remain only in this browser tab and is not sent to Qira.

DEEPER / THE REAL STATIC ANALYZER

Run zizmor. Inspect the actual findings here.

The free check above uses Qira's limited patterns. For a broader GitHub Actions audit, use zizmor—an independent security analyzer with YAML-aware rules. Run it on your own computer or in your own GitHub Actions, then bring its JSON report back to this page.

Qira does not execute zizmor in your browser, receive your files, run your workflow, or claim these findings were independently verified. This viewer accepts zizmor JSON v1 reports and processes them locally.

01 / RUN THE ENGINE

Generate the full findings file

With uv installed, open your Git repository root and run:

uvx --from zizmor==1.32.0 zizmor --offline --strict-collection --no-exit-codes --format=json-v1 --collect=workflows . > zizmor-results.json

Pinned to zizmor 1.32.0. It runs offline audits after uv downloads the analyzer. The JSON includes real zizmor rule IDs, severity, confidence, and locations. Output documentation.

Prefer GitHub Actions?

Use the official zizmor integration guide in your own repository. The JSON-v1 command above is the supported import format here; SARIF is not accepted by this viewer.

02 / READ THE RESULT

Inspect zizmor's original JSON

Select the zizmor-results.json file generated on your computer. Its contents stay in this browser tab.

Maximum 2 MB, up to 2,000 findings. No account, token, upload, or repository connection.

A report can be modified before you open it. This viewer does not authenticate the originating tool, confirm the repository state, or certify a remediation.

STEP 3 / GO BEYOND PATTERNS

The free check flags lines.
The paid review assesses context.

A suspicious-looking line is not a verified risk. For an authorized repository, Qira checks source evidence, documents uncertainty, prioritizes recommendations and gives your team concrete verification checks.

Inspect the real LOLM source study · Explore the sample report