Linus Torvalds' Condemnation — "GitHub is Pure Garbage"
Before discussing the compromise of GitHub Actions, we need to clarify the relationship between Git itself and GitHub.
Git is a distributed version control system developed in 2005 by Linus Torvalds — the creator of the Linux kernel. However, Torvalds has repeatedly leveled harsh criticism at GitHub, which was built on top of the Git he created.
In September 2021, in connection with a pull request for the NTFS driver in Linux 5.15, Torvalds wrote the following on the kernel mailing list:
"GitHub creates completely useless garbage merges. You should never merge using the GitHub interface."
"Git comes with a proper pull request generation module, but GitHub decided to replace it entirely with their own inferior version."
"GitHub pull requests and online commit editing are pure garbage."
What Torvalds takes issue with is that GitHub's merge commit messages end up as uninformative strings like "Merge branch 'torvalds:master' into master" — completely destroying the context of what was merged and why. For mission-critical projects like kernel development, this is not merely an aesthetic problem but a fundamental undermining of code traceability and quality assurance.
Torvalds' criticism does not deny GitHub's value as a code hosting platform (he has also said "it's fine as hosting"). However, the creator of Git himself warned early on that GitHub's workflow — pull requests, merges, and the GitHub Actions built on top of them — carries serious design flaws.
The Chain of GitHub Actions Compromises — A Devastating Record of 2025–2026
From 2025 to 2026, supply chain attacks targeting GitHub Actions cascaded at an unprecedented scale.
March 2025: tj-actions/changed-files Compromise. CVE-2025-30066 (CVSS 8.6). Starting from a PAT (Personal Access Token) leaked via a pull_request_target vulnerability in SpotBugs, attackers built an attack chain through reviewdog/action-setup → tj-actions/changed-files → Coinbase agentikit. A Base64-encoded payload dumped CI/CD runner memory, exposing all environment variables and secrets in workflow logs. More than 23,000 repositories were affected, with Docker Hub, npm, and AWS credentials exposed in 218 repositories. CISA added this to the Known Exploited Vulnerabilities (KEV) catalog on March 18 and issued a formal alert. The primary target was Coinbase's agentikit project, reportedly aimed at cryptocurrency theft.
November 2025: The Shai-Hulud Worm. Discovered by Unit 42 researchers at Palo Alto Networks. It trojaned over 700 npm packages, created 27,000 malicious GitHub repositories, and exposed 14,000 secrets across 487 organizations within hours. It built a self-propagating botnet-like network where compromised systems shared access tokens. Zapier, ENS Domains, PostHog, and Postman were temporarily trojaned.
2025: UNC6395 / Salesloft Breach. Called "the largest SaaS breach campaign of the year," it affected more than 700 organizations. Attackers accessed Salesloft's GitHub account, downloaded code, added guest accounts, and configured unauthorized workflows. Using stolen OAuth tokens, they accessed hundreds of Salesforce environments. Affected organizations include Cloudflare, SentinelOne, Zscaler, Palo Alto Networks, Google, PagerDuty, and Proofpoint.
March 2026: Trivy-action Compromise. An autonomous bot called "hackerbot-claw," belonging to threat actor "TeamPCP," exploited pull_request_target workflows to steal PATs and force-pushed overwrites to 76 of the 77 tags in aquasecurity/trivy-action, extracting SSH keys, cloud provider credentials, database credentials, Kubernetes tokens, and cryptocurrency wallets. CVE-2025-61671 (CVSS 9.3, Critical) was assigned, and Microsoft published security guidance.
The Full Picture of Attack Vectors — Anatomy of Structural Vulnerabilities
GitHub Actions compromises stem not from individual misconfigurations, but from structural vulnerabilities inherent to the architecture.
Privilege escalation through improper use of pull_request_target. The standard pull_request trigger executes in the context of the fork's origin and holds only read-only access. However, pull_request_target runs in the context of the target branch (main) and carries full secret access and a read-write GITHUB_TOKEN. An attacker need only submit a PR from a fork to gain access to all secrets in the target repository. OWASP classifies this as CICD-SEC-04 (Poisoned Pipeline Execution), and MITRE ATT&CK registers it as T1677. In February 2026, the autonomous bot "hackerbot-claw" exploited this vulnerability in at least six prominent repositories.
"Typosquatting" attacks on the GitHub Marketplace. In a proof-of-concept (PoC) experiment by Orca Security, 14 fake organizations were created (e.g., "circelci," "actons," "docker-action"), and the "actons" organization was referenced by 12 repositories within 2 months with zero promotion. GitHub has no mechanism to verify the authenticity of Actions, and anyone can publish an Action under a name similar to a popular one. This constitutes a low-cost, high-impact supply chain attack.
Abuse of OIDC (OpenID Connect) trust relationships. Keyless authentication to AWS/GCP/Azure using GitHub Actions OIDC tokens can allow any GitHub Actions workflow to access cloud resources if IAM role trust policies are misconfigured. Tinder Security Labs and Datadog Security Labs have published detailed research on this, and AWS took measures in June 2025 to restrict the creation of new vulnerable roles.
Runner environment hijacking and cryptocurrency mining. The Shai-Hulud campaign installed unauthorized runners on compromised machines and deliberately used vulnerable workflows as C2 channels. NVIDIA researchers obtained a reverse shell from a self-hosted g5g.metal instance runner. Praetorian Research concluded that "self-hosted GitHub runners are backdoors," warning that non-ephemeral runners become persistent attack footholds.
GitHub's Own Confession — "Visibility Is Limited, Control Is Minimal"
Most striking is that GitHub itself acknowledged structural weaknesses in its 2026 Actions Security Roadmap.
GitHub officially admits: "Action dependencies are resolved at runtime and are non-deterministic," "visibility is limited," "control is minimal," "over-permissioned workflows," "unclear trust boundaries," and "configurations that are easy to misconfigure" — all of which are the root causes that enabled the attacks described above.
Nirmata published an article in March 2026 titled "GitHub Actions is Under Attack," summarizing the escalating threats. Sysdig's research found that even security-focused open source repositories such as MITRE and Splunk were using insecure GitHub Actions. The OpenSSF (Open Source Security Foundation) published a "CI/CD Pipeline Security Guide" in response to the tj-actions and reviewdog attacks.
GitLab Self-Hosted — The Rise of the "Ultimate Private Factory"
As structural vulnerabilities in GitHub Actions are exposed, self-hosted GitLab is rapidly gaining support as the "ultimate private factory for the vibe coding era."
The fundamental advantage of self-hosted GitLab is its lack of dependency on third-party marketplace Actions. Every GitHub Actions compromise has stemmed from a breakdown in the marketplace's trust model. GitLab provides SAST, DAST, dependency scanning, container scanning, secret detection, and license compliance all built-in, with no reliance on external plugins. Runners are also self-managed by design, eliminating dependency on shared infrastructure.
GitLab Community Edition is completely free and can be self-hosted, running on either Kubernetes or bare-metal Linux. This stands in contrast to GitHub Enterprise, which requires an enterprise plan for self-hosting. Approximately half of all GitLab instances are operated as self-hosted deployments, demonstrating overwhelming demand for on-premises management.
The Vibe Coding Era and Data Sovereignty — Why GitLab Now
In early 2026, 92% of U.S. developers have adopted vibe coding (AI-assisted development). The AI-assisted coding tools market is projected to reach $8.5 billion in 2026. Yet the reality is that approximately 24.7% of AI-generated code contains security flaws, and around 45% harbor vulnerabilities. In early 2026, an app developed through vibe coding caused a massive data breach, exposing 1.5 million API keys.
GitLab Duo Self-Hosted (GA in February 2025, v17.9) is a structural answer to this risk. By deploying the LLM within the customer's own infrastructure, inference data never leaves the customer's network. It supports Mistral models (on vLLM), Claude 3.5 Sonnet (on AWS Bedrock), and OpenAI models (on Azure OpenAI). In v18.4, Model Selection (administrators choose the model vendor used for AI workflows), Context Exclusion (exclude sensitive files/directories from AI context), and Knowledge Graph (the foundation for deeper RAG + code intelligence integration) are available in GA/beta.
For heavily regulated industries — finance, healthcare, government, and defense — the guarantee that proprietary code is never sent to external AI providers and never used as AI training data is not a security requirement; it is a business requirement.
Adoption in Government, Defense, and Regulated Industries
GitLab self-hosted is adopted in environments with the most stringent security requirements.
GitLab Dedicated for Government has obtained FedRAMP Moderate and TX-RAMP certifications. Hardened images are integrated into the Department of Defense's Iron Bank and can be deployed across the entire DoD at all classification levels. GitLab Duo Self-Hosted operates in air-gapped environments — classified facilities, secure private clouds, and regulated data centers. US government support is handled exclusively by US citizens.
Major enterprises such as Airbus, NVIDIA, Siemens, and Goldman Sachs have adopted it, and HIPAA-compliant healthcare environments come standard with more than 50 compliance controls. Data residency, isolation, and private networking are provided in the customer's chosen region.
GitLab's Financial Performance — The Numbers Behind Rapid Growth
GitLab Inc. (NASDAQ: GTLB) results reflect the rapid expansion of self-hosted demand.
FY2026 (fiscal year ending January 2026) revenue was $955 million (approximately ¥143.25 billion), up 25.8% year-over-year. Q2 FY2026 revenue was $236 million (up 29%). Dollar-based net retention rate was 121%. Customers with ARR over $100,000 reached 1,344 (up 25%), and customers with ARR over $5,000 reached 10,338 (up 11%). Registered users exceed 30 million. Remaining performance obligations (RPO) were $988 million (up 32%).
Analyst consensus on the stock is Strong Buy (24 Buy, 5 Hold, 0 Sell). The median price target is $56.50, with the highest target at $75.00 (Macquarie's Steve Koenig).
DevSecOps Market — Supply Chain Security is the Fastest Growing
The GitHub Actions compromise chain is driving growth across the entire DevSecOps market.
The DevSecOps market is projected to expand from approximately $10 billion in 2025 and approximately $11.4 billion in 2026, to $26–37 billion in 2032–2035 (CAGR 14.6–17.8%). The supply chain security segment is growing at the fastest CAGR — precisely the area where GitHub Actions vulnerabilities have been exposed.
VC investment is also concentrating in the DevSecOps space: Opsera (AI-powered DevOps, Series B $20M), Pixee (automated code remediation, seed $15M), Boost Security (DevSecOps automation, seed $12M). 70% of funding is flowing into North American startups, led by Decibel Partners, Shield Capital, and Paladin Capital.
Future Outlook — Two Diverging Paths
GitHub Actions and GitLab self-hosted embody two fundamentally different philosophies about the future of development infrastructure.
GitHub's strengths lie in extensibility through 10,000+ Marketplace Actions and the network effects of over 100 million developers. 90% of the Fortune 100 uses GitHub. However, the structural weaknesses acknowledged in its 2026 security roadmap——"dependencies resolved at runtime," "minimal control," and "configurations that are easy to misconfigure"——are architectural-level problems that cannot be solved with patches.
GitLab self-hosted follows the philosophy of "build everything in-house, control everything." It completely eliminates the marketplace trust model and provides SAST/DAST/secret detection as built-in features. For requirements such as AI data sovereignty in the vibe coding era, deployment in air-gapped environments, and regulatory compliance for government, finance, and healthcare——GitLab self-hosted is rapidly establishing its position as the "ultimate private factory" that meets these demands.
OWASP's Poisoned Pipeline Execution (CICD-SEC-04) underlies all major incidents involving GitHub Actions. As long as this attack vector exists, the security of GitHub Actions remains structurally unstable. GitLab's integrated, self-contained architecture eliminates this risk at the design level.
Impact on the Industry
First, the chain of GitHub Actions compromises in 2025–2026 demonstrates that CI/CD supply chain security has been elevated from a "nice-to-have" to an "existential business issue." tj-actions (23,000 repositories), Shai-Hulud (14,000 secrets across 487 organizations), UNC6395 (700 companies), Trivy (CVSS 9.3) — the cumulative impact of these incidents risks causing a fundamental loss of trust in GitHub Actions' marketplace model.
Second, GitHub's own acknowledgment that "visibility is limited" and "control is minimal" officially confirms the existence of a structural problem. This is an issue that requires architectural-level redesign rather than patches, and a short-term resolution is unlikely.
Third, the emergence of self-hosted GitLab as the "ultimate private factory" is driven by a combination of motivations: AI data sovereignty in the vibe-coding era, air-gap requirements for government and defense, regulatory compliance for finance and healthcare, and structural departure from GitHub Actions' supply chain risks. The numbers — FY2026 revenue of $955 million (+25.8%), 1,344 customers with ARR exceeding $100,000 (+25%) — substantiate the strength of this demand.
Fourth, the fact that the supply chain security segment of the DevSecOps market is the fastest growing means that GitHub Actions vulnerabilities are reshaping market structure. GitLab stands to be the greatest beneficiary of this wave.
References: CISA Alert CVE-2025-30066 & CVE-2025-30154 (March 2025), Unit 42 GitHub Actions Supply Chain Attack Targeting Coinbase, Wiz tj-actions/changed-files Analysis, Wiz reviewdog/action-setup Analysis, Hunters Security tj-actions & reviewdog Report, The Hacker News CISA Warning, The Hacker News Trivy Breach (March 2026), Palo Alto Networks Trivy Supply Chain Attack, Microsoft Security Blog Trivy Compromise, Unit 42 Shai-Hulud npm Supply Chain Attack, Wiz Shai-Hulud 2.0, eSecurity Planet UNC6395 GitHub Breach 700+ Companies, Obsidian Security UNC6395 Salesloft, Codecov Post-Mortem (April 2021), Linus Torvalds LKML (September 2021), The Register GitHub Merges Criticism, Orca Security Typosquatting in GitHub Actions, Orca Security pull_request_target Exploits, Upwind hackerbot-claw RCE, Adnan Khan GitHub Actions Cache Poisoning, Datadog GitHub-to-AWS Keyless Authentication Flaws, Tinder Security Labs OIDC Vulnerabilities, Sysdig Self-Hosted Runners as Backdoors, Synacktiv Hijacking GitHub Runners, OWASP CICD-SEC-04, MITRE ATT&CK T1677, Alex Birsan Dependency Confusion, OpenSSF CI/CD Security Guide, Nirmata "GitHub Actions is Under Attack" (March 2026), GitHub Blog 2026 Actions Security Roadmap, Sysdig Insecure Actions in MITRE/Splunk, GitLab FY2026 Q2/Q3 Financial Results, GitLab Federal Government Solutions, GitLab FedRAMP Authorization, GitLab HIPAA Compliance, GitLab Duo Self-Hosted Documentation, InfoQ GitLab Self-Hosted AI, GitLab npm Supply Chain Attack Discovery, Fortune Business Insights DevSecOps Market, Precedence Research DevSecOps Market, DEV Community Securing Vibe Coded Applications 2026, Daily.dev Vibe Coding 2026, MarketBeat/StockAnalysis GTLB Forecast