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

Qira Proof / review protocol

What we check—and what we do not

The boundaries, method and evidence of the founding GitHub Actions configuration review.

Scope and authorization

The founding review covers one customer-authorized GitHub repository and up to 20 GitHub Actions workflow files. Repository access is opt-in and read-only where available. A customer should never email GitHub tokens, passwords, private keys or cloud credentials to us.

The subject is workflow configuration: action references, declared permissions, selected triggers and text patterns related to trust. It is not an assessment of application source-code correctness, infrastructure penetration testing, runtime account privileges, or all possible supply-chain exposures.

Changes after the collected snapshot may alter the results. A deliverable should identify the repository, commit or revision, coverage and collection date. Findings not backed by a source location are not acceptable evidence.

Current paid handoff: Stripe's hosted checkout is followed by manual receipt verification, customer identity confirmation, scoped repository authorization, and human delivery. The website return page does not grant access automatically.

How an observation becomes a finding

  • Collect bounded evidence. Inspect the authorized workflow files without downloading unrelated customer content.
  • Run the bounded workflow pattern checks. They identify selected text and YAML structures, not the full effective runtime context.
  • Corroborate against source. A reviewer checks the line, its YAML placement, and whether the relevant step or job can actually execute.
  • Document uncertainty. Separate the directly observed configuration from possible outcomes, conditional branches and unexamined controls.
  • Deliver prioritized next steps. Explain which checks the engineering team should perform and what must be verified before claiming remediation.

For example, an action referenced by a version tag can be reported as a mutable reference; the source line does not prove that the action is malicious. A declared id-token: write scope can be reported as a capability request; it does not prove an external cloud role was assumed.

What a customer receives

  • Source-linked findings with file and line references, not just a severity badge.
  • A description of what was directly observed and what remains unknown.
  • A prioritized written set of review or remediation recommendations.
  • A coverage and limitations statement for the selected snapshot.
  • A machine-readable JSON integrity receipt for the reported evidence.

Delivery timing and repository scope are confirmed after purchase. The $299 founding product is a one-time human-reviewed service, not an automated monitoring subscription or a security certification.

Where the scanner stops

The research scanner has a deliberately bounded parser. It does not perform full YAML semantic evaluation for all anchors, aliases, inline expressions or unusual syntax. Unsupported patterns should be marked uncertain rather than converted into a confident negative.

A workflow file is not a faithful record of every security control that applies at runtime. Effective permissions can be affected by repository and organization policy, event context, third-party infrastructure, environment protections and credential configuration.

Our pinned LOLM source review demonstrates three source-corroborated workflow observations. Two additional Python control-flow defects on that page were found manually, not by the workflow scanner. The study is first-party and not independently certified.

Evidence standard and conflicts

A reviewer must be able to reconstruct the claim from a stable source line. When the source contradicts a generated explanation, the explanation must change. Where uncertainty cannot be resolved without access not granted by the customer, we label the limit.

The strongest next evidence is independently adjudicated representative workflows and a completed paid order-to-deliverable pilot. We do not claim either has already been completed.

UNDERSTAND THE WHOLE OFFER

See the source. A pinned, first-party LOLM case shows what we actually examined. See the format. The synthetic sample shows how an action plan is structured. See the scope. The $299 page explains what an authorized buyer receives.

Real evidenceInteractive specimenWhat $299 includes