Version updated for https://github.com/mizcausevic-dev/otel-genai-diff-action to version v0.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary The otel-genai-diff-action GitHub Action automates the validation of changes in OTel GenAI rollup reports within pull requests by calculating structured diffs between the current and previous report versions. It identifies and flags significant cost or token usage increases (with a default 10% threshold), posts the analysis as a PR comment, and optionally fails the build for breaking changes. This action streamlines the review process by ensuring cost efficiency and consistency across AI tooling updates.

Version updated for https://github.com/mizcausevic-dev/otel-genai-fleet-summary-action to version v0.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary The otel-genai-fleet-summary-action GitHub Action automates the analysis of OpenTelemetry GenAI OTLP span exports, identifying governance issues such as unauthorized model usage, missing attributes, and high error rates. It posts a Markdown summary of findings as a pull request comment and can fail builds when high-severity issues are detected, ensuring compliance and improving oversight of large language model (LLM) trace data across fleets. Key capabilities include error rate monitoring, model validation, and integration with other governance tools in the Kinetic Gain Suite.

Version updated for https://github.com/mizcausevic-dev/procurement-pulse-action to version v0.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action evaluates a domain’s compliance with the Kinetic Gain Protocol Suite by probing its /.well-known/ paths and calculating a disclosure score (0–100) and tier ranking. It automates tasks such as self-scoring on pull requests, gating releases based on compliance thresholds, publishing score badges, and generating timestamped JSON receipts of the evaluation. This action helps organizations monitor and maintain protocol adherence, prevent regressions, and streamline compliance reporting.

Version updated for https://github.com/mizcausevic-dev/prompt-provenance-diff-action to version v0.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary The Prompt Provenance Diff Action is a GitHub Action designed to automate the validation of changes to a prompt-provenance JSON document in pull requests. It detects and flags breaking changes, such as alterations to prompt hashes, approval states, or document lineage, posts a structured diff as a PR comment, and can fail the build if necessary. This action helps ensure document integrity and compliance with predefined provenance protocols, streamlining the review process for prompt-related changes.

Version updated for https://github.com/mizcausevic-dev/prompt-provenance-fleet-summary-action to version v0.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary The prompt-provenance-fleet-summary-action is a GitHub Action designed to analyze a directory of prompt-provenance documents, identify governance gaps, and count prompts by their approval states. It automates the generation of a Markdown summary, posts it as a pull request comment, and optionally fails the build if high-severity issues are detected. This action streamlines governance and compliance checks for prompt-provenance documentation, ensuring quality and accountability in prompt management workflows.

Version updated for https://github.com/mizcausevic-dev/prompt-provenance-readme-generator-action to version v0.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary The prompt-provenance-readme-generator-action is a GitHub Action that automates the process of generating a user-friendly Markdown README file from a structured prompt-provenance JSON document. It addresses the need for maintaining clear and consistent documentation by either posting the rendered README as a comment on pull requests or saving it to a specified file path. This action streamlines documentation updates and integrates seamlessly with workflows to ensure alignment between the JSON source and its corresponding README.

Version updated for https://github.com/mmnto-ai/totem to version @mmnto/pack-rust-architecture@1.53.0. This action is used across all versions by 0 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Totem is a file-based toolkit designed to enhance collaboration between developers and AI coding agents by maintaining architectural consistency and context throughout a project. It provides a deterministic linting engine, a queryable knowledge index, and markdown-based lessons to prevent common coding mistakes and ensure reuse of existing solutions. By combining offline validation with optional LLM-powered features, Totem automates code reviews, enforces architectural rules, and reduces friction caused by repetitive errors in AI-assisted development workflows.

Version updated for https://github.com/moonrunnerkc/swarm-orchestrator to version v10.4.0-advisory. This action is used across all versions by 0 repositories. Action Type This is a Docker action. Go to the GitHub Marketplace to find the latest changes. Action Summary Swarm Orchestrator is a GitHub Action and CLI tool designed to audit AI-generated pull requests by analyzing their diffs, scoring them with advisory-grade cheat detectors, and providing suspicion-score comments along with compliance artifacts (e.g., CycloneDX-ML and SPDX AI-Profile). It automates the detection of potential issues in PRs and supports both advisory (non-blocking) and gate (merge-blocking) modes, addressing the need for enhanced code review and compliance with AI-related regulations. Key capabilities include advanced detection, compliance reporting, and compatibility with AI procurement standards like the EU AI Act.

Version updated for https://github.com/Pro-Bandey/multi-style-snake-contribution-grid to version v01.06.26. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action, Multi-Style Snake Contribution Grid, automates the creation of dynamic, animated visualizations of a user’s GitHub contribution graph. It generates customizable snake animations with five unique themes, geometric shapes, and labeled months, producing high-quality SVG and GIF outputs for easy sharing or embedding in profile READMEs. The action simplifies the process by automatically detecting the repository owner, running on a schedule or manually, and generating an organized gallery in a dedicated branch.

Version updated for https://github.com/procyon-creative/jira-action-man to version v2.1.0. This action is used across all versions by 1 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary The Jira Action Man GitHub Action automates the process of identifying Jira issue keys from GitHub events (e.g., branch names, PR titles, commit messages, PR body) and integrates them with Jira by posting PR descriptions as comments on corresponding Jira tickets. It streamlines workflows by enabling automatic issue linking, updating Jira tickets with PR details, and uploading PR body images as attachments, while offering configurable filters, regex patterns, and Jira comment management options. This action is ideal for teams looking to enhance traceability and communication between GitHub and Jira.