Skip to content

[deep-report] Security Scan workflow schedule has been disabled since 2026-01-16 while its config keeps getting patched #60032

Closed as not planned

Description

@github-actions

Description

.github/workflows/security-scan.yml (the repo's gosec + govulncheck daily security gate) had its GitHub Actions schedule manually disabled on 2026-01-16 (confirmed live via actions_get: "state":"disabled_manually", "updated_at":"2026-01-16T00:13:21Z"). Its last recorded run is #45 from 2026-01-15T06:02:55Z (41/41 recorded runs failed, per list_workflow_runs).

Despite the schedule being off for ~8 months, the workflow file itself has kept receiving active gosec/govulncheck maintenance commits well after the disable date — e.g. "fix(security): pin govulncheck to go.mod version..." (2026-06-27), "fix(gosec): align to v2.27.1, enforce nosec policy flags..." (2026-06-05), "Update gosec to v2.28.0..." (2026-07-15), and "Migrate tools.go to Go 1.24 tool directives; remove dead gosec config..." (2026-07-29). None of these changes have ever actually been validated by CI, because the workflow that would run them has not executed since January.

Why this matters: this is a silent CI blind spot distinct from "the gate is failing" — it's a gate that quietly stopped running at all 8 months ago while contributors kept patching its config in good faith, with no automated signal telling anyone the schedule was off.

Expected Impact

Restores actual CI validation of gosec/govulncheck security scanning (or, if the team decides scheduled gosec scanning is no longer wanted — e.g. superseded by CodeQL/other tooling — removes a misleading dead workflow file so future contributors stop maintaining config nobody runs).

Suggested Agent

Repository Quality Improvement Agent (repository-quality-improver) or a maintainer — this is a decision + fix task (re-enable after fixing the gosec exclusion baseline, or delete the workflow), not pure investigation.

Estimated Effort

Quick (< 1 hour) to re-enable via gh workflow enable/API once a decision is made; Medium if choosing to fix the gosec finding backlog first.

Data Source

DeepReport Intelligence Briefing analysis, 2026-09-10 cycle (window since briefing #59970), cross-referencing Repository Quality Improvement Report #59977 with live mcp__github__actions_get/list_workflow_runs/list_commits verification. Note: #59977 itself did not check the workflow's enabled/disabled state and incorrectly framed this as an actively-running-but-silently-failing daily gate — it has not run at all since 2026-01-16.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

  • api.anthropic.com
  • proxy.golang.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.anthropic.com"
    - "proxy.golang.org"

See Network Configuration for more information.

Generated by 🔬 Deep Report · claude · agent · 239.2 AIC · ⌖ 12.5 AIC · ⊞ 12.8K · ◷

  • expires on Sep 12, 2026, 10:39 AM UTC-08:00

Activity

  1. github-actions commented on Sep 12, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-09-12T18:39:13.036Z.

    Closed by Workflow

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions