A tool in the ImagineQira ecosystem / Source-backed clarity01 — GITHUB WORKFLOW INTELLIGENCE
Qira Proof / public specimen

Example report.

A look at how Qira Proof separates configuration observations from interpretation. These three examples are synthetic, not results from a customer repository.

QIRA PROOF / EXAMPLE REPORT / 01 OF 03SYNTHETIC · NOT A LIVE SCAN
CONFIGURATION / EXTERNAL ACTION

Mutable external action reference

The sample workflow invokes actions/checkout@v4. A tag can move independently of the workflow file. This is a source-backed inspection prompt—not evidence of compromise.

SOURCE / LINE
.github/workflows/build-and-release.yml : 27
OBSERVATION TYPE
Direct configuration observation; behavioral risk unverified.
WORKFLOW YAML / SOURCE EXCERPTFICTIONAL DEMONSTRATION
25  - name: Checkout
26    # Synthetic example
27    uses: actions/checkout@v4
WHAT THIS DOES NOT PROVE
Whether the referenced revision is approved, malicious or exploitable cannot be established from this YAML line alone.
HUMAN-REVIEW NEXT ACTION
Review the action publisher and resolved revision. Use a reviewed commit digest when that matches repository policy.

This is a three-record illustrative report. No repository was scanned to generate these examples; the paid service is a bounded, human-reviewed configuration assessment, not a security certification.

TRY THE DELIVERABLE / INTERACTIVE

Turn observations into a fix plan.

Use this fictional three-finding workbook to try a practical part of the service: assign work, mark progress, and export a developer-ready checklist. All data stays in this browser tab. It does not scan a repository, record a customer action, or update GitHub.

0 of 3 resolvedSelect a status for each example.
01 / ACTION PINNINGReview before release

Mutable action reference

Source: Fictional workflow line 27 · actions/checkout@v4

Change: Review the action's publisher and select an approved, full-length commit revision if required by policy.

Accept when: The intended action revision is independently identified, the reference matches the approved revision, and the workflow runs successfully.

02 / TOKEN SCOPEVerify required access

Declared OIDC permission

Source: Fictional workflow line 8 · id-token: write

Change: Check the actual jobs and cloud trust policies, then limit unnecessary write capability.

Accept when: Each permission is justified by a job, the intended OIDC trust is documented, and the workflows still perform their authorized tasks.

03 / HOST TRUSTConfirm independent trust

SSH key collected at runtime

Source: Fictional workflow line 44 · ssh-keyscan

Change: Locate an independently obtained expected host fingerprint and compare it before trusting the host.

Accept when: The accepted host key matches the approved fingerprint and the deployment path fails closed on mismatch.

A plan the engineer can take away.

Exports a Markdown checklist with source, next action, acceptance criteria, owner, and current status. Clearly labeled synthetic.

No sample data leaves this browser.

Want to see evidence that comes from an actual repository rather than invented examples? Open the pinned LOLM case study ↗ · What the $299 review includes ↗