harnessguard 0.1.0__tar.gz

harnessguard-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: CI
+
+on:
+  push:
+    branches: [master, main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --all-groups
+      - name: Lint
+        run: uv run ruff check .
+      - name: Tests
+        run: uv run pytest
+      - name: Self-scan (vulnerable fixture; report only)
+        run: uv run harnessguard scan fixtures/vulnerable-repo --fail-on none --sarif harnessguard-vulnerable.sarif
+      - name: Self-scan (clean fixture; must pass)
+        run: uv run harnessguard scan fixtures/clean-repo --fail-on low

harnessguard-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,19 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  pypi:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - name: Build
+        run: uv build
+      - name: Publish to PyPI (trusted publishing)
+        run: uv publish

harnessguard-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.py[cod]
+.venv/
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+*.sarif
+.DS_Store

harnessguard-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

harnessguard-0.1.0/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.5
+Name: harnessguard
+Version: 0.1.0
+Summary: Static hardening linter for GitHub Actions workflows that run AI agents — Agent Rule of Two, OWASP ASI mapping. Never executes anything.
+Project-URL: Homepage, https://github.com/dtduc-git/harnessguard
+Project-URL: Issues, https://github.com/dtduc-git/harnessguard/issues
+Project-URL: Changelog, https://github.com/dtduc-git/harnessguard/releases
+Author-email: Duke - Duc Dinh <dtduc.contact@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai-agents,cicd,github-actions,owasp,prompt-injection,sarif,sast,security,supply-chain
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.7
+Requires-Dist: typer>=0.12
+Description-Content-Type: text/markdown
+
+# harnessguard
+
+Static hardening linter for GitHub Actions workflows that run **AI agents**.
+
+Agents in CI (Claude Code Action, Gemini CLI Action, Codex, Copilot agents and
+friends) read attacker-controlled text — issue bodies, PR titles, comments —
+while the runner holds secrets and write tokens. That combination is the new
+CI/CD supply-chain attack surface: a public comment becomes instructions the
+agent obeys.
+
+harnessguard enforces Microsoft's **[Agents Rule of Two](https://www.microsoft.com/en-us/security/blog/2026/06/05/securing-ci-cd-in-agentic-world-claude-code-github-action-case)**:
+an AI-powered workflow must never combine untrusted input, privileged access,
+and external communication. It runs as a **static, deterministic** check in
+pull requests — it never executes your workflows or your agents.
+
+## Why
+
+Real incidents, all from 2026:
+
+- **Comment and Control** (April 2026) — hijacked Claude Code Security Review,
+  Gemini CLI Action and Copilot Agent via PR titles / issue bodies; leaked
+  `ANTHROPIC_API_KEY`, `GEMINI_API_KEY` and `GITHUB_TOKEN` through public
+  comments.
+- **Black Hat USA 2026** (August) — an unprivileged GitHub issue reached CI
+  runner secrets in the vendors' own repositories; Gemini CLI Action got
+  CVE-2026-12537 (CVSS 10.0).
+- **MSRC** — Claude Code Action's Read tool reached `/proc/self/environ`;
+  fixed in 2.1.128.
+
+Existing Actions linters (`zizmor`, `actionlint`, `poutine`…) are excellent
+but agent-blind: they don't model "this step is an LLM that will obey text."
+
+## Install
+
+```bash
+pip install harnessguard
+# or from source
+uv sync && uv run harnessguard --version
+```
+
+## Usage
+
+```bash
+# scan the current repo (finds .github/workflows/)
+harnessguard scan .
+
+# fail CI on high and above, write SARIF for code scanning
+harnessguard scan . --fail-on high --sarif harnessguard.sarif
+
+# machine-readable output
+harnessguard scan . --format json
+
+# list rules
+harnessguard rules list
+```
+
+Exit code is 1 when findings at or above `--fail-on` exist. `--fail-on none`
+reports without failing.
+
+### GitHub Action
+
+```yaml
+name: harnessguard
+on: [push, pull_request]
+
+jobs:
+  harnessguard:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      security-events: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: dtduc-git/harnessguard@main
+        with:
+          fail-on: high
+```
+
+## Rules
+
+| Rule  | Severity | What it catches |
+|-------|----------|-----------------|
+| HG001 | critical | Agent step on untrusted events with secrets in scope |
+| HG002 | high | Attacker-controlled event data interpolated into an agent step |
+| HG003 | high | Agent step on untrusted events with write permissions |
+| HG004 | high | Agent step in a `pull_request_target` workflow |
+| HG005 | medium | Agent step with shell/network tool grants or egress commands |
+
+Findings map to the OWASP Top 10 for Agentic Applications (ASI01–ASI03).
+Rules are data — YAML in `src/harnessguard/rules_data/` — and checks are small
+named functions in `checks.py`. Add your own with `--rules-dir`.
+
+## Design principles
+
+- **Never executes anything.** No workflow runs, no agent calls, no network.
+- **Local-first.** No account, no telemetry, no SaaS.
+- **Deterministic.** Same input → same findings; no LLM in the detection path.
+- **Rules as data.** Extend coverage without touching the engine.
+
+## Non-goals
+
+- Not a general-purpose Actions linter — use zizmor alongside it.
+- No runtime enforcement or proxy — that is a different (complementary) tool.
+- Not GitLab/Jenkins (yet).
+
+## References
+
+- Microsoft Security Blog — *Securing CI/CD in an agentic world* (Agents Rule
+  of Two), June 2026
+- CSA — *Comment and Control: GitHub AI Agents as Credential Exfiltrators*,
+  April 2026
+- OWASP — Top 10 for Agentic Applications 2026
+
+## License
+
+Apache-2.0

harnessguard-0.1.0/README.md

@@ -0,0 +1,116 @@
+# harnessguard
+
+Static hardening linter for GitHub Actions workflows that run **AI agents**.
+
+Agents in CI (Claude Code Action, Gemini CLI Action, Codex, Copilot agents and
+friends) read attacker-controlled text — issue bodies, PR titles, comments —
+while the runner holds secrets and write tokens. That combination is the new
+CI/CD supply-chain attack surface: a public comment becomes instructions the
+agent obeys.
+
+harnessguard enforces Microsoft's **[Agents Rule of Two](https://www.microsoft.com/en-us/security/blog/2026/06/05/securing-ci-cd-in-agentic-world-claude-code-github-action-case)**:
+an AI-powered workflow must never combine untrusted input, privileged access,
+and external communication. It runs as a **static, deterministic** check in
+pull requests — it never executes your workflows or your agents.
+
+## Why
+
+Real incidents, all from 2026:
+
+- **Comment and Control** (April 2026) — hijacked Claude Code Security Review,
+  Gemini CLI Action and Copilot Agent via PR titles / issue bodies; leaked
+  `ANTHROPIC_API_KEY`, `GEMINI_API_KEY` and `GITHUB_TOKEN` through public
+  comments.
+- **Black Hat USA 2026** (August) — an unprivileged GitHub issue reached CI
+  runner secrets in the vendors' own repositories; Gemini CLI Action got
+  CVE-2026-12537 (CVSS 10.0).
+- **MSRC** — Claude Code Action's Read tool reached `/proc/self/environ`;
+  fixed in 2.1.128.
+
+Existing Actions linters (`zizmor`, `actionlint`, `poutine`…) are excellent
+but agent-blind: they don't model "this step is an LLM that will obey text."
+
+## Install
+
+```bash
+pip install harnessguard
+# or from source
+uv sync && uv run harnessguard --version
+```
+
+## Usage
+
+```bash
+# scan the current repo (finds .github/workflows/)
+harnessguard scan .
+
+# fail CI on high and above, write SARIF for code scanning
+harnessguard scan . --fail-on high --sarif harnessguard.sarif
+
+# machine-readable output
+harnessguard scan . --format json
+
+# list rules
+harnessguard rules list
+```
+
+Exit code is 1 when findings at or above `--fail-on` exist. `--fail-on none`
+reports without failing.
+
+### GitHub Action
+
+```yaml
+name: harnessguard
+on: [push, pull_request]
+
+jobs:
+  harnessguard:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      security-events: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: dtduc-git/harnessguard@main
+        with:
+          fail-on: high
+```
+
+## Rules
+
+| Rule  | Severity | What it catches |
+|-------|----------|-----------------|
+| HG001 | critical | Agent step on untrusted events with secrets in scope |
+| HG002 | high | Attacker-controlled event data interpolated into an agent step |
+| HG003 | high | Agent step on untrusted events with write permissions |
+| HG004 | high | Agent step in a `pull_request_target` workflow |
+| HG005 | medium | Agent step with shell/network tool grants or egress commands |
+
+Findings map to the OWASP Top 10 for Agentic Applications (ASI01–ASI03).
+Rules are data — YAML in `src/harnessguard/rules_data/` — and checks are small
+named functions in `checks.py`. Add your own with `--rules-dir`.
+
+## Design principles
+
+- **Never executes anything.** No workflow runs, no agent calls, no network.
+- **Local-first.** No account, no telemetry, no SaaS.
+- **Deterministic.** Same input → same findings; no LLM in the detection path.
+- **Rules as data.** Extend coverage without touching the engine.
+
+## Non-goals
+
+- Not a general-purpose Actions linter — use zizmor alongside it.
+- No runtime enforcement or proxy — that is a different (complementary) tool.
+- Not GitLab/Jenkins (yet).
+
+## References
+
+- Microsoft Security Blog — *Securing CI/CD in an agentic world* (Agents Rule
+  of Two), June 2026
+- CSA — *Comment and Control: GitHub AI Agents as Credential Exfiltrators*,
+  April 2026
+- OWASP — Top 10 for Agentic Applications 2026
+
+## License
+
+Apache-2.0

harnessguard-0.1.0/SECURITY.md

@@ -0,0 +1,13 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Please report vulnerabilities privately via GitHub Security Advisories:
+https://github.com/dtduc-git/harnessguard/security/advisories/new
+
+Do not open a public issue for security problems.
+
+## Scope
+
+harnessguard is a static analyzer. It never executes scanned workflows, agents
+or MCP servers, and it makes no network requests during a scan.

harnessguard-0.1.0/action.yml

@@ -0,0 +1,41 @@
+name: harnessguard
+description: Static hardening linter for GitHub Actions workflows that run AI agents. Never executes anything.
+author: dtduc-git
+branding:
+  icon: shield
+  color: red
+
+inputs:
+  paths:
+    description: Files or directories to scan
+    required: false
+    default: "."
+  fail-on:
+    description: "Exit 1 at this severity or above: critical | high | medium | low | info | none"
+    required: false
+    default: "high"
+  sarif-file:
+    description: SARIF output path
+    required: false
+    default: "harnessguard.sarif"
+
+runs:
+  using: composite
+  steps:
+    - uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    - name: Install harnessguard
+      shell: bash
+      run: pip install harnessguard || pip install "git+https://github.com/dtduc-git/harnessguard"
+    - name: Scan
+      shell: bash
+      run: |
+        harnessguard scan ${{ inputs.paths }} \
+          --fail-on ${{ inputs.fail-on }} \
+          --sarif ${{ inputs.sarif-file }}
+    - name: Upload SARIF
+      if: always()
+      uses: github/codeql-action/upload-sarif@v3
+      with:
+        sarif_file: ${{ inputs.sarif-file }}

harnessguard-0.1.0/fixtures/clean-repo/.github/workflows/release-notes.yml

@@ -0,0 +1,22 @@
+name: Release notes agent
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: Release version
+        required: true
+
+permissions:
+  contents: read
+
+jobs:
+  notes:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Draft notes
+        uses: anthropics/claude-code-action@v1
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          prompt: "Draft release notes for version ${{ inputs.version }}"
+          claude_args: '--allowedTools "Read"'

harnessguard-0.1.0/fixtures/vulnerable-repo/.github/workflows/review.yml

@@ -0,0 +1,12 @@
+name: PR review agent
+on: pull_request_target
+
+jobs:
+  review:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.pull_request.head.ref }}
+      - name: Gemini review
+        run: npx @google/gemini-cli --prompt "Review the diff in this pull request"

harnessguard-0.1.0/fixtures/vulnerable-repo/.github/workflows/triage.yml

@@ -0,0 +1,20 @@
+name: Issue triage agent
+on:
+  issues:
+    types: [opened]
+
+permissions:
+  contents: write
+  issues: write
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Claude triage
+        uses: anthropics/claude-code-action@v1
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          prompt: "Triage this issue: ${{ github.event.issue.title }} — ${{ github.event.issue.body }}"
+          claude_args: '--allowedTools "Bash,Write,Read"'