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.
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.
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.
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 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.