plugin-scanner 2.0.580__tar.gz → 2.0.582__tar.gz

plugin_scanner-2.0.582/.github/workflows/publish-action-repo.yml

@@ -0,0 +1,205 @@
+name: Publish GitHub Action Repository
+
+on:
+  workflow_dispatch:
+    inputs:
+      scanner_version:
+        description: "Optional plugin-scanner version to publish (defaults to latest hol-guard release)"
+        required: false
+        default: ""
+  workflow_run:
+    workflows: ["Publish to PyPI"]
+    types: [completed]
+    branches: [main]
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ai-plugin-scanner-action-repo-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  publish-action-repo:
+    name: Sync action repo + publish release notes
+    if: >-
+      github.event_name == 'workflow_dispatch' ||
+      (github.event.workflow_run.conclusion == 'success' &&
+       github.event.workflow_run.event == 'push' &&
+       github.event.workflow_run.head_branch == 'main')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    env:
+      ACTION_REPOSITORY: hashgraph-online/ai-plugin-scanner-action
+      SOURCE_REF: ${{ github.event_name == 'workflow_run' && github.event.workflow_run.head_sha || github.sha }}
+      SOURCE_REPOSITORY: ${{ github.repository }}
+      SOURCE_SERVER_URL: ${{ github.server_url }}
+    steps:
+      - name: Validate publication credentials
+        env:
+          ACTION_REPO_TOKEN: ${{ secrets.ACTION_REPO_TOKEN }}
+        run: |
+          if [ -z "$ACTION_REPO_TOKEN" ]; then
+            echo "ACTION_REPO_TOKEN must be configured to publish the GitHub Action repository." >&2
+            exit 1
+          fi
+
+      - name: Checkout source repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
+        with:
+          ref: ${{ env.SOURCE_REF }}
+          fetch-depth: 0
+
+      - name: Resolve published scanner version
+        id: scanner_version
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          REQUESTED_VERSION: ${{ inputs.scanner_version }}
+        run: |
+          if [ -n "$REQUESTED_VERSION" ]; then
+            VERSION="$REQUESTED_VERSION"
+          else
+            VERSION="$(gh release list --repo "$SOURCE_REPOSITORY" --limit 1 --json tagName --jq '.[0].tagName | ltrimstr("v")')"
+          fi
+
+          if [ -z "$VERSION" ]; then
+            echo "Could not resolve plugin-scanner version to publish." >&2
+            exit 1
+          fi
+
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+
+      - name: Compute scanner wheel SHA256
+        id: scanner_sha256
+        env:
+          SCANNER_VERSION: ${{ steps.scanner_version.outputs.version }}
+        run: |
+          python3 -m pip install --disable-pip-version-check --no-input "pypi-attestations==$(tr -d '[:space:]' < action/pypi-attestations-version.txt)"
+          DIST_DIR="${RUNNER_TEMP}/scanner-wheel"
+          mkdir -p "$DIST_DIR"
+          WHEEL_PATH=""
+          for attempt in 1 2 3 4 5 6 7 8 9 10; do
+            rm -f "$DIST_DIR"/plugin_scanner-*.whl
+            if python3 -m pip download --disable-pip-version-check --no-input --only-binary=:all: --no-deps --dest "$DIST_DIR" "plugin-scanner==${SCANNER_VERSION}"; then
+              WHEEL_PATH="$(find "$DIST_DIR" -maxdepth 1 -name 'plugin_scanner-*.whl' -print | sort | head -n1)"
+              if [ -n "$WHEEL_PATH" ]; then
+                break
+              fi
+            fi
+            if [ "$attempt" -eq 10 ]; then
+              echo "Could not download plugin-scanner wheel for version ${SCANNER_VERSION} after waiting for PyPI propagation." >&2
+              exit 1
+            fi
+            echo "plugin-scanner==${SCANNER_VERSION} not on PyPI yet; retrying in 30s (attempt ${attempt}/10)..."
+            sleep 30
+          done
+          SHA256="$(python3 -c "import hashlib,sys; print(hashlib.sha256(open(sys.argv[1],'rb').read()).hexdigest())" "$WHEEL_PATH")"
+          echo "sha256=$SHA256" >> "$GITHUB_OUTPUT"
+
+      - name: Compute next action release tag
+        id: version
+        env:
+          GH_TOKEN: ${{ secrets.ACTION_REPO_TOKEN }}
+        run: |
+          LAST_TAG=$(gh release list --repo "$ACTION_REPOSITORY" --limit 1 --json tagName --jq '.[0].tagName // ""')
+
+          if [ -z "$LAST_TAG" ]; then
+            TAG="v1.0.0"
+          else
+            IFS=. read -r MAJOR MINOR PATCH <<< "${LAST_TAG#v}"
+            if [ -z "$MAJOR" ] || [ -z "$MINOR" ] || [ -z "$PATCH" ]; then
+              echo "Unsupported release tag format: $LAST_TAG" >&2
+              exit 1
+            fi
+            TAG="v${MAJOR}.${MINOR}.$((PATCH + 1))"
+          fi
+
+          echo "tag=$TAG" >> "$GITHUB_OUTPUT"
+
+      - name: Clone action repository
+        env:
+          GH_TOKEN: ${{ secrets.ACTION_REPO_TOKEN }}
+        run: gh repo clone "$ACTION_REPOSITORY" action-repo -- --depth 1
+
+      - name: Configure authenticated action repository remote
+        working-directory: action-repo
+        env:
+          ACTION_REPO_TOKEN: ${{ secrets.ACTION_REPO_TOKEN }}
+        run: |
+          git remote set-url origin "https://x-access-token:${ACTION_REPO_TOKEN}@github.com/${ACTION_REPOSITORY}.git"
+
+      - name: Sync root-ready action bundle
+        working-directory: action-repo
+        run: |
+          cp "${GITHUB_WORKSPACE}/action/action.yml" action.yml
+          cp "${GITHUB_WORKSPACE}/action/README.md" README.md
+          cp "${GITHUB_WORKSPACE}/action/CONTRIBUTING.md" CONTRIBUTING.md
+          cp "${GITHUB_WORKSPACE}/action/SECURITY.md" SECURITY.md
+          printf '%s\n' "${{ steps.scanner_version.outputs.version }}" > scanner-version.txt
+          printf '%s\n' "${{ steps.scanner_sha256.outputs.sha256 }}" > scanner-sha256.txt
+          cp "${GITHUB_WORKSPACE}/action/cisco-version.txt" cisco-version.txt
+          cp "${GITHUB_WORKSPACE}/action/pypi-attestations-version.txt" pypi-attestations-version.txt
+          cp "${GITHUB_WORKSPACE}/LICENSE" LICENSE
+
+      - name: Detect sync changes
+        id: diff
+        working-directory: action-repo
+        run: |
+          if [ -n "$(git status --short -- action.yml README.md CONTRIBUTING.md SECURITY.md scanner-version.txt scanner-sha256.txt cisco-version.txt pypi-attestations-version.txt LICENSE)" ]; then
+            echo "changed=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "changed=false" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Commit synced bundle
+        if: steps.diff.outputs.changed == 'true'
+        working-directory: action-repo
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git add action.yml README.md CONTRIBUTING.md SECURITY.md scanner-version.txt scanner-sha256.txt cisco-version.txt pypi-attestations-version.txt LICENSE
+          git commit -m "chore: publish action bundle ${{ steps.version.outputs.tag }} (plugin-scanner ${{ steps.scanner_version.outputs.version }})"
+
+      - name: Push action repository branch and tags
+        if: steps.diff.outputs.changed == 'true'
+        working-directory: action-repo
+        run: |
+          TAG="${{ steps.version.outputs.tag }}"
+          git push origin HEAD:main
+          git tag "$TAG"
+          git push origin "refs/tags/${TAG}"
+          git tag -fa v1 -m "Update floating major tag to ${TAG}"
+          git push origin refs/tags/v1 --force
+
+      - name: Check action release state
+        id: release_state
+        working-directory: action-repo
+        env:
+          GH_TOKEN: ${{ secrets.ACTION_REPO_TOKEN }}
+        run: |
+          TAG="${{ steps.version.outputs.tag }}"
+
+          if gh release view "${TAG}" --repo "$ACTION_REPOSITORY" >/dev/null 2>&1; then
+            echo "release_exists=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "release_exists=false" >> "$GITHUB_OUTPUT"
+          fi
+
+          if git ls-remote --tags origin "refs/tags/${TAG}" | grep -q .; then
+            echo "tag_exists=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "tag_exists=false" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Create action repository release
+        if: steps.release_state.outputs.release_exists == 'false' && (steps.diff.outputs.changed == 'true' || steps.release_state.outputs.tag_exists == 'true')
+        env:
+          GH_TOKEN: ${{ secrets.ACTION_REPO_TOKEN }}
+        run: |
+          TAG="${{ steps.version.outputs.tag }}"
+          gh release create "${TAG}" \
+            --repo "$ACTION_REPOSITORY" \
+            --title "$TAG" \
+            --generate-notes \
+            --notes "Published automatically from ${SOURCE_SERVER_URL}/${SOURCE_REPOSITORY}/tree/${SOURCE_REF} with plugin-scanner ${{ steps.scanner_version.outputs.version }}."

{plugin_scanner-2.0.580 → plugin_scanner-2.0.582}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plugin-scanner
-Version: 2.0.580
+Version: 2.0.582
 Summary: Lint, verify, and gate plugin ecosystems for maintainers, CI, and publish workflows.
 Project-URL: Homepage, https://github.com/hashgraph-online/hol-guard
 Project-URL: Repository, https://github.com/hashgraph-online/hol-guard
@@ -641,7 +641,7 @@ repos:
 
 The Marketplace action lives in the dedicated repository [hashgraph-online/ai-plugin-scanner-action](https://github.com/hashgraph-online/ai-plugin-scanner-action).
 
-This repository no longer vendors a local action bundle. Use the standalone action repository for `action.yml`, release notes, and action-specific documentation. The legacy alias [hashgraph-online/hol-codex-plugin-scanner-action](https://github.com/hashgraph-online/hol-codex-plugin-scanner-action) remains available for existing workflows.
+The Marketplace action bundle is maintained in [`action/`](./action) and published automatically to [hashgraph-online/ai-plugin-scanner-action](https://github.com/hashgraph-online/ai-plugin-scanner-action) by [`.github/workflows/publish-action-repo.yml`](./.github/workflows/publish-action-repo.yml) after each PyPI release. The legacy alias [hashgraph-online/hol-codex-plugin-scanner-action](https://github.com/hashgraph-online/hol-codex-plugin-scanner-action) remains available for existing workflows.
 When you run the scanner in your own job instead of the packaged action, install `plugin-scanner[cisco]` on Python 3.11+ and set `CISCO_MCP_SCAN=auto` or `CISCO_MCP_SCAN=on` for full Cisco MCP coverage.
 
 ### Plugin Author Submission Flow

{plugin_scanner-2.0.580 → plugin_scanner-2.0.582}/README.md

@@ -599,7 +599,7 @@ repos:
 
 The Marketplace action lives in the dedicated repository [hashgraph-online/ai-plugin-scanner-action](https://github.com/hashgraph-online/ai-plugin-scanner-action).
 
-This repository no longer vendors a local action bundle. Use the standalone action repository for `action.yml`, release notes, and action-specific documentation. The legacy alias [hashgraph-online/hol-codex-plugin-scanner-action](https://github.com/hashgraph-online/hol-codex-plugin-scanner-action) remains available for existing workflows.
+The Marketplace action bundle is maintained in [`action/`](./action) and published automatically to [hashgraph-online/ai-plugin-scanner-action](https://github.com/hashgraph-online/ai-plugin-scanner-action) by [`.github/workflows/publish-action-repo.yml`](./.github/workflows/publish-action-repo.yml) after each PyPI release. The legacy alias [hashgraph-online/hol-codex-plugin-scanner-action](https://github.com/hashgraph-online/hol-codex-plugin-scanner-action) remains available for existing workflows.
 When you run the scanner in your own job instead of the packaged action, install `plugin-scanner[cisco]` on Python 3.11+ and set `CISCO_MCP_SCAN=auto` or `CISCO_MCP_SCAN=on` for full Cisco MCP coverage.
 
 ### Plugin Author Submission Flow

plugin_scanner-2.0.582/action/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contributing to AI Plugin Scanner
+
+Thanks for contributing to `ai-plugin-scanner`.
+
+This repository ships:
+
+- `hol-guard` for local harness protection
+- `plugin-scanner` for CI and maintainer checks across supported AI plugin ecosystems
+- `codex-plugin-scanner` as a compatibility package alias
+
+## Before You Start
+
+- Search existing [issues](https://github.com/hashgraph-online/ai-plugin-scanner/issues) before opening a new report.
+- Use [discussions](https://github.com/hashgraph-online/ai-plugin-scanner/discussions) for design questions, proposals, and broader feedback.
+- Open a pull request for code or documentation changes. PRs against `main` are the normal contribution path.
+
+## Development Setup
+
+```bash
+git clone https://github.com/hashgraph-online/ai-plugin-scanner.git
+cd ai-plugin-scanner
+uv sync --extra dev
+```
+
+If you prefer a virtualenv-first workflow, the repository can also be installed in editable mode:
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+## Validation Requirements
+
+All non-trivial changes should include or update automated tests.
+
+Run the standard validation commands before opening or updating a pull request:
+
+```bash
+# If using uv:
+uv run python -m ruff check src tests
+uv run python -m ruff format --check src tests
+uv run pytest --tb=short
+
+# If using pip (with the virtualenv activated):
+python -m ruff check src tests
+python -m ruff format --check src tests
+pytest --tb=short
+```
+
+If you changed packaging or release logic, also verify the build:
+
+```bash
+# If using uv:
+uv run python -m build
+
+# If using pip:
+python -m build
+```
+
+## Contribution Process
+
+1. Fork the repository.
+2. Create a feature branch from `main`.
+3. Make the smallest coherent change that fixes the issue or adds the feature.
+4. Add or update tests for new functionality and changed behavior.
+5. Run the validation commands above.
+6. Open a pull request against `main` with a clear summary of what changed and why.
+
+## Contribution Expectations
+
+- Python code should remain compatible with the versions declared in `pyproject.toml`.
+- Keep command examples and package names aligned with the current product names: `hol-guard`, `plugin-scanner`, and `ai-plugin-scanner`.
+- Update user-facing docs when the CLI surface, GitHub Action contract, trust scoring behavior, or published workflows change.
+- Do not commit secrets, credentials, or local environment files.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under Apache-2.0.

plugin_scanner-2.0.582/action/README.md

@@ -0,0 +1,280 @@
+# HOL AI Plugin Scanner GitHub Action
+
+[![Latest Release](https://img.shields.io/github/v/release/hashgraph-online/ai-plugin-scanner-action?display_name=tag)](https://github.com/hashgraph-online/ai-plugin-scanner-action/releases/latest)
+[![Marketplace Repository](https://img.shields.io/badge/github-marketplace_repo-0A84FF)](https://github.com/hashgraph-online/ai-plugin-scanner-action)
+[![Compatibility Alias](https://img.shields.io/badge/compat-hol--codex--plugin--scanner--action-6b7280)](https://github.com/hashgraph-online/hol-codex-plugin-scanner-action)
+[![Source of Truth](https://img.shields.io/badge/source-hol--guard-111827)](https://github.com/hashgraph-online/hol-guard/tree/main/action)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](https://github.com/hashgraph-online/hol-guard/blob/main/LICENSE)
+
+| ![Hashgraph Online Logo](https://hol.org/brand/Logo_Whole_Dark.png) | Marketplace-ready GitHub Action for scanning AI plugin repositories across Codex, Claude, Gemini, and OpenCode ecosystems for security, publishability, runtime readiness, and trust signals. The action emits structured reports, SARIF, policy results, and submission metadata while staying aligned to the main scanner release train.<br><br>[Latest Release](https://github.com/hashgraph-online/ai-plugin-scanner-action/releases/latest)<br>[Marketplace Repository](https://github.com/hashgraph-online/ai-plugin-scanner-action)<br>[Compatibility Alias](https://github.com/hashgraph-online/hol-codex-plugin-scanner-action)<br>[Scanner Source of Truth](https://github.com/hashgraph-online/hol-guard/tree/main/action)<br>[Report an Issue](https://github.com/hashgraph-online/hol-guard/issues) |
+| :--- | :--- |
+
+This repository is the canonical Marketplace-facing wrapper for the scanner action. The hol-guard repository remains the source of truth, while this published action bundle keeps the required root `action.yml` layout for GitHub Marketplace.
+
+The legacy action slug `hashgraph-online/hol-codex-plugin-scanner-action@v1` remains supported as a compatibility alias for existing workflows. New integrations should use `hashgraph-online/ai-plugin-scanner-action@v1`.
+
+The default Marketplace install path uses an exact `plugin-scanner` PyPI release, verifies its PyPI provenance against `hashgraph-online/hol-guard`, and only then installs it. After installation, the default `scan`, `lint`, and offline `verify` paths operate on local repository content only. Live network probing and submission automation remain explicit opt-in features.
+
+Advanced distribution paths are available when you need them:
+
+- `install_source: local` is the explicit dogfood path for `uses: ./action` inside the source repo.
+- `ghcr.io/hashgraph-online/hol-guard` is the container distribution for enterprise runners that prefer a reviewed OCI image over runtime package installation.
+
+## Usage
+
+```yaml
+- name: Scan AI Plugin Repository
+  uses: hashgraph-online/ai-plugin-scanner-action@v1
+  with:
+    plugin_dir: "./my-plugin"
+    min_score: 70
+    fail_on_severity: high
+```
+
+## Inputs
+
+| Input | Description | Default |
+|-------|-------------|---------|
+| `plugin_dir` | Path to a single plugin directory or a repo marketplace root | `.` |
+| `mode` | Execution mode: `scan`, `lint`, `verify`, or `submit` | `scan` |
+| `format` | Output format: `text`, `json`, `markdown`, `sarif` | `text` |
+| `output` | Write report to this file path | `""` |
+| `profile` | Policy profile: `default`, `public-marketplace`, or `strict-security` | `default` |
+| `config` | Optional path to a scanner config file such as `.plugin-scanner.toml` | `""` |
+| `baseline` | Optional path to a baseline suppression file | `""` |
+| `online` | Enable live network probing for `verify` mode | `false` |
+| `upload_sarif` | Upload the generated SARIF report to GitHub code scanning when `mode: scan` | `false` |
+| `sarif_category` | SARIF category used during GitHub code scanning upload | `ai-plugin-scanner` |
+| `write_step_summary` | Write a concise markdown summary to the GitHub Actions job summary | `true` |
+| `registry_payload_output` | Write a machine-readable plugin ecosystem payload JSON file for registry or awesome-list automation | `""` |
+| `min_score` | Fail if score is below this threshold (0-100) | `0` |
+| `fail_on_severity` | Fail on findings at or above this severity: `none`, `critical`, `high`, `medium`, `low`, `info` | `none` |
+| `cisco_skill_scan` | Cisco skill-scanner mode: `auto`, `on`, `off` | `auto` |
+| `cisco_policy` | Cisco policy preset: `permissive`, `balanced`, `strict` | `balanced` |
+| `install_cisco` | Install the opt-in Cisco skill-scanner dependency used by this repo | `false` |
+| `install_source` | Package install source: `pypi` for the reviewed release path, or `local` for source-repo dogfooding | `pypi` |
+| `submission_enabled` | Open submission issues for awesome-list and registry automation when the plugin clears the submission threshold | `false` |
+| `submission_score_threshold` | Minimum score required before a submission issue is created | `80` |
+| `submission_repos` | Comma-separated GitHub repositories that should receive the submission issue | `hashgraph-online/awesome-codex-plugins` |
+| `submission_token` | Required when `submission_enabled` is `true`; use a token with `issues:write` access to the submission repositories | `""` |
+| `submission_labels` | Comma-separated labels to apply when creating submission issues | `plugin-submission` |
+| `submission_category` | Listing category included in the submission issue body | `Community Plugins` |
+| `submission_plugin_name` | Override the plugin name used in the submission issue | `""` |
+| `submission_plugin_url` | Override the plugin repository URL used in the submission issue | `""` |
+| `submission_plugin_description` | Override the plugin description used in the submission issue | `""` |
+| `submission_author` | Override the plugin author used in the submission issue | `""` |
+| `pr_comment` | PR comment mode: `auto`, `always`, or `off` | `auto` |
+| `pr_comment_style` | PR comment style: `concise` or `detailed` | `concise` |
+| `pr_comment_max_findings` | Maximum findings to include in PR comment summaries | `5` |
+
+## Outputs
+
+| Output | Description |
+|--------|-------------|
+| `score` | Numeric score (0-100) |
+| `grade` | Letter grade (A-F) |
+| `grade_label` | Human-readable grade label |
+| `policy_pass` | `true` when the selected policy profile passed |
+| `verify_pass` | `true` when runtime verification passed |
+| `max_severity` | Highest finding severity, or `none` |
+| `findings_total` | Total number of findings across all severities |
+| `report_path` | Path to the rendered report file, if `output` was set |
+| `registry_payload_path` | Path to the machine-readable plugin ecosystem payload file, if requested |
+| `submission_eligible` | `true` when the plugin met the submission threshold and passed the configured severity gate |
+| `submission_performed` | `true` when a submission issue was created or an existing one was reused |
+| `submission_issue_urls` | Comma-separated submission issue URLs |
+| `submission_issue_numbers` | Comma-separated submission issue numbers |
+| `action_exit_code` | Action execution exit code |
+| `pr_comment_status` | PR comment status (`created`, `updated`, `unchanged`, `skipped`, `disabled`) |
+| `pr_comment_id` | PR comment ID when available |
+| `pr_comment_url` | PR comment URL when available |
+
+The action also writes a concise summary to `GITHUB_STEP_SUMMARY` by default. The full report is written to the job log for `text` output, or to the file you pass through `output` for `json`, `markdown`, or `sarif`.
+
+Mode notes:
+
+- `scan` and `lint` respect `profile`, `config`, and `baseline`.
+- `verify` respects `online` and writes a human-readable report for `format: text`.
+- `submit` writes the plugin-quality artifact to `output` when provided, otherwise `plugin-quality.json`. `registry_payload_output` remains dedicated to the separate HOL registry payload.
+- `online`, `submission_enabled`, and `upload_sarif` are the only common paths that intentionally reach beyond the runner after the scanner package itself has been installed.
+- `pr_comment_status` currently defaults to `skipped` in this Marketplace wrapper path.
+
+## Examples
+
+### Basic scan with minimum score gate
+
+```yaml
+- uses: hashgraph-online/ai-plugin-scanner-action@v1
+  with:
+    plugin_dir: "."
+    min_score: 70
+```
+
+### SARIF output for GitHub Code Scanning
+
+```yaml
+permissions:
+  contents: read
+  security-events: write
+
+jobs:
+  scan:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: hashgraph-online/ai-plugin-scanner-action@v1
+        with:
+          plugin_dir: "."
+          mode: scan
+          format: sarif
+          fail_on_severity: high
+          upload_sarif: true
+```
+
+This `plugin_dir: "."` pattern is correct for both single-plugin repositories and multi-plugin marketplace repositories. When `.agents/plugins/marketplace.json` exists, the action switches into repository mode and scans each local plugin entry declared under `./plugins/...`.
+
+### With Cisco skill scanning
+
+```yaml
+- uses: hashgraph-online/ai-plugin-scanner-action@v1
+  with:
+    plugin_dir: "."
+    cisco_skill_scan: on
+    cisco_policy: strict
+    install_cisco: true
+```
+
+### Dogfood the source-repo action bundle
+
+Use this only inside `hashgraph-online/hol-guard`, where the action can install the adjacent source tree directly.
+
+```yaml
+- uses: ./action
+  with:
+    plugin_dir: "."
+    install_source: local
+```
+
+### Export registry payload for ecosystem automation
+
+```yaml
+- uses: hashgraph-online/ai-plugin-scanner-action@v1
+  id: scan
+  with:
+    plugin_dir: "."
+    format: sarif
+    upload_sarif: true
+    registry_payload_output: ai-plugin-registry-payload.json
+
+- name: Show trust signals
+  run: |
+    echo "Score: ${{ steps.scan.outputs.score }}"
+    echo "Grade: ${{ steps.scan.outputs.grade_label }}"
+    echo "Max severity: ${{ steps.scan.outputs.max_severity }}"
+```
+
+The registry payload mirrors the submission metadata used by HOL ecosystem automation, so the same scan can feed trust scoring, registry ingestion, badges, or awesome-list processing without reparsing the terminal output.
+
+### Score 80+ and auto-file an awesome-list submission issue
+
+When the scan reaches `80+` and does not trip the configured severity gate, the action opens or reuses a submission issue in `hashgraph-online/awesome-codex-plugins`. The issue body includes a machine-readable registry payload so downstream registry automation can ingest the same submission event.
+
+```yaml
+permissions:
+  contents: read
+
+jobs:
+  scan:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Scan plugin and submit if eligible
+        id: scan
+        uses: hashgraph-online/ai-plugin-scanner-action@v1
+        with:
+          plugin_dir: "."
+          min_score: 80
+          fail_on_severity: high
+          submission_enabled: true
+          submission_score_threshold: 80
+          submission_token: ${{ secrets.AWESOME_CODEX_PLUGINS_TOKEN }}
+
+      - name: Show submission issue
+        if: steps.scan.outputs.submission_performed == 'true'
+        run: echo "${{ steps.scan.outputs.submission_issue_urls }}"
+```
+
+Use a fine-grained token with `issues:write` on `hashgraph-online/awesome-codex-plugins`. `submission_token` is required when `submission_enabled: true`. The action deduplicates by an exact hidden plugin URL marker in the issue body, so repeated pushes reuse the open submission issue instead of opening duplicates.
+
+### Markdown report as PR comment
+
+```yaml
+- uses: hashgraph-online/ai-plugin-scanner-action@v1
+  id: scan
+  with:
+    plugin_dir: "."
+    format: markdown
+    output: scan-report.md
+
+- name: Comment PR
+  uses: actions/github-script@v7
+  with:
+    script: |
+      const fs = require('fs');
+      const report = fs.readFileSync('scan-report.md', 'utf8');
+      github.rest.issues.createComment({
+        issue_number: context.issue.number,
+        owner: context.repo.owner,
+        repo: context.repo.repo,
+        body: report
+      });
+```
+
+## Release Management
+
+- Publish immutable releases for this Marketplace wrapper repository automatically from the source scanner repo when `action/` changes merge to `main`.
+- Move the floating major tag `v1` to the latest compatible release.
+- Keep the canonical action in its own public repository for GitHub Marketplace publication.
+- Keep the legacy action repository synchronized as a compatibility alias for existing consumers.
+- Configure `ACTION_REPO_TOKEN` as a secret in the source repository so `publish-action-repo.yml` can automatically sync the canonical and legacy action repositories, create releases, and publish autogenerated release notes.
+- Optionally set `ACTION_CANONICAL_REPOSITORY` or `ACTION_COMPAT_REPOSITORY` in the source repository if the targets differ from the defaults.
+- Sync the install metadata files (`scanner-version.txt`, `cisco-version.txt`, and `pypi-attestations-version.txt`) with the action bundle so both action repositories always install the same reviewed scanner release.
+
+## Source of Truth
+
+The source bundle for this action lives in the main scanner repository under `action/`. Release artifacts from that repository should export a root-ready action bundle for the dedicated action repositories.
+
+Direct edits in published action repositories should stay limited to Marketplace-specific copy or metadata. Functional changes and release publication logic belong in `hashgraph-online/ai-plugin-scanner` so merges there can publish matching action releases automatically.
+
+## License
+
+[Apache-2.0](https://github.com/hashgraph-online/hol-guard/blob/main/LICENSE)
+
+## Mode-based workflow
+
+Set `mode` to one of `scan`, `lint`, `verify`, or `submit`.
+
+```yaml
+- uses: hashgraph-online/ai-plugin-scanner-action@v1
+  with:
+    mode: verify
+    plugin_dir: "."
+```
+
+For `submit` mode, point `plugin_dir` at one concrete plugin directory. Repository-mode discovery is supported for `scan`, `lint`, and `verify`, but `submit` intentionally remains single-plugin.
+
+For `scan` mode, set `upload_sarif: true` to emit and upload SARIF automatically instead of wiring a separate upload step by hand.
+
+## Container Distribution
+
+The scanner is also published as an OCI image for container-first environments:
+
+```bash
+docker run --rm \
+  -v "$PWD:/workspace" \
+  ghcr.io/hashgraph-online/hol-guard:<version> \
+  scan /workspace --format text
+```
+
+The image installs the scanner from the reviewed source tree at release build time. It is separate from the Marketplace action so teams that prefer `docker://` or explicit `docker run` flows can use a pinned image without changing the secure default action path.

plugin_scanner-2.0.582/action/SECURITY.md

@@ -0,0 +1,43 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported |
+|---------|-----------|
+| 2.x     | Yes       |
+| 1.x     | No        |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in `ai-plugin-scanner`, please report it privately:
+
+1. Do not open a public issue for the vulnerability.
+2. Email `security@hol.org`.
+3. Include the affected package or surface (`hol-guard`, `plugin-scanner`, GitHub Action, container image, or release workflow).
+4. Include reproduction steps, impact, and any known mitigations.
+
+We aim to:
+
+- acknowledge vulnerability reports within 48 hours
+- provide an initial triage response within 14 days
+- resolve confirmed issues as quickly as practical based on severity and release risk
+
+## Scope
+
+This policy covers:
+
+- the Python packages published from this repository
+- the reviewed container image
+- the GitHub Action bundle sourced from this repository
+- release and automation workflows maintained in this repository
+
+## Secure Use Guidance
+
+For users of the project:
+
+- keep the scanner and Guard packages updated to the latest supported release line
+- review plugin code and MCP configuration before enabling it in a local harness
+- avoid committing secrets, API keys, or local environment files into plugin repositories
+- prefer HTTPS-only remote endpoints and pinned GitHub Actions in plugin repositories
+
+The scanner and Guard help identify risky patterns, but they are not a substitute for manual review or a full secure development lifecycle.