auditing-gha

Diff GitHub Actions settings against a canonical baseline to surface drift.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill auditing-gha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auditing-gha
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/auditing-gha
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill auditing-gha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff a fleet repository's GitHub Actions settings against the canonical baseline to surface drift and misconfigurations. Read-only: surfaces what to change, doesn't change it.

Core Features & Use Cases

  • Drift detection for per-repo Action permissions and allowed patterns against the fleet baseline.
  • Guidance for remediation via the web UI or admin API; supports onboarding and periodic health checks.
  • Produces human-readable findings and, optionally, machine-readable output for automation.

Quick Start

Run the auditing-gha skill against a fleet repository to detect drift in Actions permissions against the canonical baseline.

Frequently Asked Questions about auditing-gha

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect GitHub Actions configuration drift across my repository fleet?▼

Detect GitHub Actions configuration drift by diffing per-repo Actions permissions and allowed patterns against a canonical fleet baseline, surfacing misconfigurations as human-readable findings for manual remediation.

Can I automatically fix GitHub Actions permissions that deviate from the baseline policy?▼

No, you cannot automatically fix GitHub Actions permissions because this auditing process is strictly read-only; it surfaces drift and provides actionable remediation guidance but requires human review to apply changes.

What is the best way to audit GitHub Actions settings during repository onboarding?▼

The best way to audit GitHub Actions settings during onboarding is to run a read-only baseline diff that identifies per-repo overrides and misconfigurations, providing actionable guidance for manual remediation.

Does the GitHub Actions baseline drift audit support machine-readable output for automation?▼

Yes, the GitHub Actions drift audit supports optional machine-readable output alongside human-readable findings, allowing you to integrate the surfaced policy violations into downstream automation pipelines.

When do I need to check GitHub Actions allowed patterns against a fleet baseline?▼

You need to check GitHub Actions allowed patterns against a fleet baseline during periodic health checks and repository onboarding to identify misconfigurations and per-repo overrides that require manual remediation.

What types of misconfigurations are surfaced when auditing GitHub Actions drift?▼

Auditing GitHub Actions drift surfaces per-repo permission overrides, deviations in allowed action patterns, and misconfigurations compared to canonical baseline patterns, all reported with actionable guidance for remediation.