Skip to content

ci: bind official CodeQL analysis uploads to producer runs - #7099

Draft
antuz123 wants to merge 248 commits into
sprintfrom
codex/r5-codeql-run-provenance
Draft

antuz123 wants to merge 248 commits into
sprintfrom
codex/r5-codeql-run-provenance

Conversation

@antuz123

Copy link
Copy Markdown
Collaborator

CodeQL Actions success previously lacked authenticated linkage to its official uploaded analysis. This follow-up captures the pinned official analyze action's sarif-id output, then verifies its original installed job/current attempt, bounded artifact/API digest, SARIF processing and exact analysis list/detail. Denied/missing/moved evidence fails closed.

Follow-up to #7085 at a1e167cab4e8485bb84418cadfb2313cbcedb644, with newly published successor #7087 546d77261d02c0633e45b2c62df8f8e5580620c0 recovered as a merge ancestor. All 114 installed-byte rejection controls are preserved. Producer branches are untouched. Base sprint follows AGENTS.md and inherits substantial history; review only this bounded delta: 546d772...bd8ad7f

The consumer also requires a separate Variables-read credential for live pin reads, with no-cache rechecks and no fallback, matching #7095's installation correction. Checkout and CodeQL actions are pinned. The receipt contains metadata only; SARIF contents are not published.

Analysis/run origin and security-result provenance remain distinct. Successful synthetic collection may record codeql_analysis_run_linkage_verified:true. The public API exposes no independent GAS-check-to-analysis-ID join; security_analysis_run_linkage_verified:false and security_check_analysis_linkage_verified:false remain explicit. All authorization flags remain false; B1 stays disabled/unintegrated.

Live permission blocker: both unfiltered and sprint-filtered GET /repos/KeeperCommunity/bitcoin-keeper/code-scanning/analyses return 403 Resource not accessible by integration, requiring security_events=read. Genuine installed receipt verification remains NOT RUN. The official GAS check 119985857101 for source 3eb92fc8a622a3e09926d49f47243c163e32d009 remains failure, despite successful Actions analysis execution; it is not cleared or waived.

Node22.23.3: node --test .github/tests/*.test.cjs scripts/trusted-release-origin.test.cjs scripts/codeql-analysis-receipt.test.cjs scripts/protected-release-plan.test.cjs 268/268 PASS; independent consumer/writer/B1 rerun 257/257 PASS. Actionlint1.7.12 on the two changed workflows PASS (external shellcheck/pyflakes disabled); whitespace PASS. The initial merged fixture run failed because inherited fixture calls omitted the new required pin credential; calls were adapted while retaining every installed-byte rejection assertion.

Installation/access handoff: r5-trusted-release-origin.md. No credential/configuration/protection change, sprint installation, native dispatch, personal Mac work, signing, upload or release-authorization activation.

Codex local handoff

State: NEEDS_LOCAL
Base: sprint
Head branch: codex/r5-codeql-run-provenance
Head commit: bd8ad7f
Goal and acceptance criteria: Authenticate official analysis-to-selected-run/current-attempt origins while preserving installed-byte controls, live pin revocation and disabled authorization.
Changes made: Official upload receipt, strict API/artifact linkage and negative controls, separate Variables reader, pinned actions, recovered #7087 successor.
Cloud checks: Exact-head268Node controls/actionlint2/whitespace PASS; independent257 targeted PASS. Live analyses API403/security_events=read; installed linkage NOT VERIFIED.
Required local checks: IOS, ANDROID
Local checks requested: Approved operator must preflight dedicated pin identity and Code Scanning read access, then verify a genuine installed sprint-push CodeQL receipt. No native dispatch is needed for CodeQL linkage. Complete canonical native receipts require separately reviewed/approved hosted execution; no personal Mac.
Risks / known gaps: Read-access denial; no installed receipt yet; GAS security-check/analysis join unverified; official prior security failure retained; full native matrix/physical acceptance and all release approvals remain separate.

antuz123 and others added 30 commits September 25, 2026 21:28
Enable the release branch test trigger and repair the inert recovery provenance fixture exposed by that run. No production app code changes.
redkeep-agents and others added 27 commits October 15, 2026 04:30
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants