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

Public repository / pinned source review

What we found in a real release workflow.

A selected source review of the public LOLM repository. Three workflow configuration observations were reproduced by Qira Proof and checked against pinned lines. Two additional release-control observations came from manual source review, outside the scanner's scope.

Jump to the actual findings ↓

Snapshot commitf9700d2e6616
Coverage1 workflow + 1 supporting script
VerificationFirst-party source cross-check
5 sourced observations3 workflow patterns · 2 separate manual findings

01 / Workflow scanner scope

Three observations corroborated against source

Configuration indicators, not severity scores or claims of exploitation.

QP-REAL-01scanner corroborated

Write permissions declared at workflow level

The workflow declares contents, pull-requests, issues, and id-token with write access.

Source evidence

contents: write · pull-requests: write · issues: write · id-token: write

What it means

These are declared token scopes. Effective privileges depend on the triggering context, repository configuration and job execution.

Next review step

Review each job's actual minimum permission needs and scope write grants to the necessary jobs.

Not established

No privilege abuse, compromise or effective runtime authorization was demonstrated.

QP-REAL-02scanner corroborated

Actions are referenced by version tags

The workflow uses actions/checkout@v7, actions/setup-python@v7 and actions/setup-node@v7 rather than full 40-character commit digests.

Source evidence

actions/checkout@v7 · actions/setup-python@v7 · actions/setup-node@v7

What it means

A tag is a movable reference. This is a provenance and supply-chain review prompt, not a claim that any referenced action is malicious.

Next review step

Identify trusted resolved revisions and evaluate pinning to reviewed immutable commit digests.

Not established

No malicious action, tag movement or exploit was established.

QP-REAL-03scanner corroborated

SSH host keys are collected at runtime

When the optional deploy-key branch runs, ssh-keyscan output is appended to known_hosts, with a command-level || true fallback.

Source evidence

ssh-keyscan -H ... >> ~/.ssh/known_hosts ... || true

What it means

Trust-on-first-use key discovery may need an independently verified expected host fingerprint. The branch is conditional; this is a source observation.

Next review step

Verify the expected host-key fingerprint out of band and fail closed when host identity cannot be established.

Not established

No network interception, incorrect host key or production exploit was observed.

02 / Separate manual review

Release-control defects found outside the scanner

These findings required reading Python control flow. They must not be presented as Qira Proof workflow-scanner detections.

QP-MANUAL-01manual source review only

An npm audit parsing failure can be counted as zero findings

The security gate catches a parsing exception and assigns high = 0, then evaluates high == 0 as a passing result.

Source evidence

except Exception: ... high = 0 ... high == 0

What it means

Malformed or unusable audit output can be treated as a clean result. This is a confirmed source-level fail-open path, not evidence that an unsafe release occurred.

Next review step

Require valid audit results and fail closed for subprocess or schema errors. Add malformed-output and nonzero-exit tests.

Not established

No actual vulnerable artifact was shown to pass through the gate.

QP-MANUAL-02manual source review only

Release operations do not require a confirmed successful merge

The script requests a merge with --admin, assigns its result to merged, but can enter the separate publish and deploy paths without checking merged.ok first.

Source evidence

gh pr merge ... --admin · merged = do_merge(...) · if pg.passed:

What it means

Publishing and deployment remain conditional on other gates and credentials. The missing merge-success dependency and administrative bypass request are control-flow concerns.

Next review step

Remove --admin, require a verified merge of the intended commit and stop on failed git operations before publishing.

Not established

No bypass of branch protection or unmerged production release was demonstrated.

Method

How to reproduce the review

Open the immutable GitHub links above, inspect the referenced source lines, then compare the three workflow observations against the scanner's recorded output. Check the separate Python claims against the exception and merge/publish branches. All claims are bounded to those files and commit.

Limitations

One workflow file and its release-control Python orchestrator; not a complete repository or runtime security audit.

Qira Proof's workflow pattern output was compared against direct reading of pinned YAML lines. The supplementary Python notes were manually reviewed outside the workflow scanner.

No external reviewer has yet adjudicated the results.

Want the same clarity for your repository?

The founding service covers one authorized repository and up to 20 workflow files, with human review and a written report.

See the $299 review
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