Skip to content

chore: refresh org SBOM inventory - #1678

Draft
opencode-agent[bot] wants to merge 577 commits into
mainfrom
automation/sbom-inventory
Draft

opencode-agent[bot] wants to merge 577 commits into
mainfrom
automation/sbom-inventory

Conversation

@opencode-agent

@opencode-agent opencode-agent Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Automated central SBOM inventory refresh for live non-fork repositories. Review reciprocal, restricted, and NOASSERTION license evidence in docs/sbom/inventory.md against the product's actual distribution and hosted-service model.


Devin Review

Current blocking state (2026-09-08)

  • Exact head: e6b292ce5e104212eaa032579afff1514b865019; live main comparison is ahead 70 / behind 0. The effective customer-evidence delta remains docs/sbom/inventory.json and docs/sbom/inventory.md.
  • required-workflow-bootstrap is deterministically RED before policy analysis because the Contents API does not inline the 1,148,611-byte JSON and protected main's policy caps that evidence path at 1 MiB. This is not an Nginx finding.
  • Canonical owner repair #1946 sits at exact head 1cb8cceb8719eb054979d84141cda9a95c0c6873, ahead 5 / behind 0, with bounded Git Blobs fallback plus malicious-content and malformed-evidence tests. Both original and Ready-event same-head Security, SAST, Python Security, and CodeQL PR runs are terminal GREEN. Noema and Strix were materialized but failed on central orchestrator/free availability (HTTP 429 / zero ready routes); OpenCode's derived CHANGES_REQUESTED contains no leaf-source finding. Keep this inventory PR Draft until fix(pingora): read Contents-API-oversized files through the Git Blobs API #1946 reaches protected main, this branch non-force integrates that release, and new exact-head checks plus independent review are valid.
  • Noema's orchestrator/free HTTP 429 is a separate review-transport blocker. Keep this PR Draft until fix(pingora): read Contents-API-oversized files through the Git Blobs API #1946 reaches protected main, this branch non-force integrates that release, and all new exact-head checks plus independent review are valid.

@opencode-agent
opencode-agent Bot requested a review from seonghobae as a code owner September 2, 2026 04:27

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

Devin Review found 3 potential issues.

⚠️ 3 issues in files not directly in the diff

⚠️ Partial inventory appears complete

With 34 of 63 SBOM fetches returning 404, repo_count reports all 63 while component totals cover only 29. The inventory presents partial organization evidence as complete.


⚠️ Permitted licenses trigger violations

For MPL-2.0 components without another prohibited license, flagged reports at least 137 policy violations. Governance therefore escalates expressly permitted dependencies.


⚠️ Permissive alternatives trigger violations

When an SPDX expression offers a permissive alternative, flagged rejects it because another alternative is copyleft. Seven selectable permissive dependencies become policy violations.

Devin Review

@seonghobae seonghobae added priority: medium Normal-priority or P2 work status: needs-review Open pull request requiring current-head review or checks type: maintenance Maintenance, build, dependency, or operational upkeep labels Sep 2, 2026 — with ChatGPT Codex Connector

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

Devin Review found 0 new potential issues.

Devin Review

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

Devin Review found 0 new potential issues.

Devin Review

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 new potential issue.

⚠️ 1 issue in files not directly in the diff

⚠️ Restricted licenses escape policy review

Seven LicenseRef-NVIDIA-Proprietary components are marked unflagged. Unknown and non-standard licenses also disappear from the commercial-permissive policy review.

Devin Review

Copy link
Copy Markdown
Contributor

Diagnosis of the required-workflow-bootstrap failure on this branch (run 33989047645, 5 s, exit 2):

Pingora edge policy could not establish complete evidence: GitHub content evidence for docs/sbom/inventory.json exceeds the size contract

This is deterministic and content-blind, not an Nginx finding. The regenerated docs/sbom/inventory.json is 1,148,611 bytes (236 bytes on main). GitHub omits the diff patch for a file that large, .json is neither a documentation suffix nor a binary document format, so pingora_edge_policy.py must fetch the content, and the Contents API stops inlining at 1 MiB (encoding: "none"), which the policy turns into a fail-closed ContentSizeExceededError. Scanned offline with main's own scan_content, the file has zero denied forms and does not contain the string nginx at all. Every push of this branch will hit the same wall until the evidence route changes.

Fix: #1946 makes the policy follow the Contents response's blob sha to the Git Blobs API (bounded at 11 MiB, bound back to the same sha and size) and scan the bytes like any inline file. Once it is on main, one push that merges main into this branch re-binds the required workflow's trusted source and this context can pass on its merits; re-running the job before then reproduces the same exit 2.


Generated by Claude Code

@cwl-noema-review cwl-noema-review Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noema LLM review

The PR refreshes several workflow concurrency groups, adds a coordinator job for CodeQL dispatch, improves allowlist parsing to support multiple trusted actors, and enhances audit coverage reporting. The changes are consistent with the stated rationales, preserve the existing authorization invariants, and introduce no confirmed concrete regressions.

Reviewed changed lines

  • .github/workflows/agent-mention-noema-dispatch.yml:17 (RIGHT): Moves concurrency from the job level to workflow level. The workflow has a single job and the job-level block is removed, so there is no same-group self-wait risk and queued runs coalesce earlier.
  • .github/workflows/agent-mention-opencode-dispatch.yml:17 (RIGHT): Moves concurrency from the job level to workflow level. The workflow has a single job and the job-level block is removed, so there is no same-group self-wait risk and queued runs coalesce earlier.
  • .github/workflows/codeql-scan-dispatch.yml:157 (RIGHT): Parses ALLOWED_DISPATCH_ACTOR as a comma-separated allowlist while requiring non-empty actors; an empty allowlist continues to admit nothing.
  • .github/workflows/codeql-scan-dispatch.yml:524 (RIGHT): The wake job condition reads validated output required_jobs and only proceeds when non-empty, avoiding a wake with missing job bindings.
  • .github/workflows/opencode-review-dispatch.yml:150 (RIGHT): Uses the same comma-separated allowlist parsing with a non-empty guard, permitting multiple trusted dispatch identities without weakening empty-list denial.

Adversarial validation

  • .github/workflows/agent-mention-noema-dispatch.yml:17 (RIGHT) falsified: Moving concurrency to workflow level could cause a run to wait on its own group when job-level and workflow-level groups match. — The diff removes the job-level concurrency block entirely, leaving only the workflow-level group, so no job requests the group its own run already holds.
  • .github/workflows/agent-mention-opencode-dispatch.yml:17 (RIGHT) falsified: Moving concurrency to workflow level could cause a run to wait on its own group when job-level and workflow-level groups match. — The diff removes the job-level concurrency block entirely, leaving only the workflow-level group, so no job requests the group its own run already holds.
  • .github/workflows/codeql-scan-dispatch.yml:157 (RIGHT) falsified: Parsing ALLOWED_DISPATCH_ACTOR with IFS=',' could produce an empty actor that is admitted. — The loop checks allowed_actor is non-empty before comparing against DISPATCH_ACTOR and DISPATCH_SENDER, so an empty allowlist admits nothing.
  • .github/workflows/codeql-scan-dispatch.yml:524 (RIGHT) falsified: Using validated output required_jobs in the wake condition could let a wake job run when no valid job ids were bound. — The wake job condition explicitly requires needs.validate-dispatch.outputs.required_jobs != '', preventing an empty jobs list from triggering the job.
  • .github/workflows/opencode-review-dispatch.yml:150 (RIGHT) falsified: Parsing ALLOWED_DISPATCH_ACTOR with IFS=',' could produce an empty actor that is admitted. — The loop checks allowed_actor is non-empty before comparing against DISPATCH_ACTOR and DISPATCH_SENDER, so an empty allowlist admits nothing.
  • Residual risk: Low. The audited probes attempted concrete regressions around deadlocks, empty allowlists, and malformed job wake inputs and were all falsified against the changed lines.

Findings

  • No blocking findings.
  • Result: APPROVE
  • Head SHA: 5f264b19eea2559b4d8ce765e158d7d414bf90eb
  • Reviewer credential: noema-review-github-app-refresh
  • Actor: cwl-noema-review[bot]

@opencode-agent

opencode-agent Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

OpenCode Review Overview

  • Head SHA: ceea8ab13058fd2d9dcfa2d02bf563e61777169e
  • Workflow run: 34194023190
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES
  • Coverage gate: success
  • Model pool: exhausted
  • Verdict: REQUEST_CHANGES

@seonghobae
seonghobae marked this pull request as draft September 8, 2026 12:18
@coderabbitai

coderabbitai Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f8dc4245-4d2c-4c32-aa34-3438f952540b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

cwl-sbom-inventory[bot] and others added 8 commits September 12, 2026 22:00
…d to the head checkout

Closes #2132. The pinned ghcr.io/google/osv-scanner-action:v2.5.1 image
warns on every run that `--output` is deprecated in favor of
`--output-file` (scanner) and `--output-files` (reporter); a bare
`--output-files=<path>` defaults to the sarif format in v2.5.1
(cmd/osv-reporter/main.go: format := "sarif" unless a `format:` prefix is
given), so the reporter output is byte-for-byte the same file. The exact
base/head checkouts live in `source`, not the workspace root, so
`upload-sarif` resolved commit identity against a non-repository and logged
"does not appear to be a git repository" twice before falling back to the
caller-supplied sha; `checkout_path` now names the real checkout.

Contract: the new test pins the non-deprecated flags, rejects the deprecated
ones, and derives the required `checkout_path` from the head checkout step's
own `path:` (removing the binding makes it fail — verified RED before GREEN).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…er job

One consumer, one runner: the standalone `changed-scope` job cost a second
runner allocation per PR org-wide purely to compute two booleans for the
`semgrep` job. The classifier now runs as a step inside `semgrep` (after
harden-runner), the expensive steps gate on `steps.scope.outputs.code`, and
the enforce step carries the same guard so a step-skipped scan's empty `rc`
cannot fail a doc-only PR. The job keeps `if: github.event.action !=
'closed'` with no needs-output term, so a doc-only run still concludes
`success` (required-workflow-path-filter-boundary.md). strix.yml is left
alone (hot-file collision zone).

Measured in #1904; contract tests updated.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…oding

Refs #2116.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
seonghobae and others added 30 commits September 19, 2026 18:03
Preserve the no-redirect production opener seam in Strix transport tests so HTTP, network, invalid JSON, and success fixtures cannot fall through to the live network.

Signed-off-by: OpenAI Codex <noreply@openai.com>
Exercise malformed authority parsing for both central clients, retain the production-opener redirect matrix, and record the exact RED/GREEN and owner Gap evidence.

This commit integrates the already-published concurrent Strix opener-seam repair at parent 663ffac without duplicating it.

Signed-off-by: OpenAI Codex <noreply@openai.com>
…boundary

fix(security): prove GitHub API URL authority
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance priority: medium Normal-priority or P2 work status: needs-review Open pull request requiring current-head review or checks type: maintenance Maintenance, build, dependency, or operational upkeep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants