agentsclimarketplace

Gh repo security audit

Skill thinkyou0714/github-flow-kit/gh-repo-security-audit

6 Claude Code skills for GitHub-native developers: pr-respond, release-notes, issue-triage, repo-tour, gh-pr-perm-audit, gh-repo-security-audit

Install
npx -y skills add thinkyou0714/github-flow-kit --skill gh-repo-security-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

OpenSSF-aligned security posture audit across all repos in a GitHub account: default workflow token permissions, allowed-actions policy, branch protection, secret scanning + push protection, and Dependabot alerts. Reports WARN (fixable gaps) vs INFO (opinionated hardening). Read-only by default; the only optional mutation is enabling Dependabot alerts. Use when you ask: "repo security audit", "OpenSSF audit", "are Dependabot alerts on?", "GitHub hardening check", "repo セキュリティ監査", "Actions セキュリティ横断". DO NOT USE FOR: writing code, changing branch protection automatically, or the PR-approval toggle (use gh-pr-perm-audit for that).

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.7 KB, as published. Nobody here has run it

GitHub Repo Security Posture Audit (OpenSSF-aligned)

Audit every repo in an account against OpenSSF Scorecard-style checks and report a clear posture. Read-only by default. The single optional mutation is enabling Dependabot alerts (a pure security gain). Everything else is reported as a human-gated recommendation. See references/openssf-checks.md for per-check rationale + sources.

Setup Check

Run gh auth status — if not authenticated, output ⚠️ gh CLI not authenticated. Run: gh auth login and stop.

Step 1: Resolve scope

  • --owner <name> or default OWNER=$(gh api user --jq .login).
  • Repos: gh repo list "$OWNER" --no-archived --limit 200 --json name --jq '.[].name'.

Step 2: Per-repo checks (GET-only)

For each repo, gather in as few calls as possible:

# one snapshot of the repo object: visibility, default branch, secret scanning
gh api "repos/$OWNER/$REPO" \
  --jq '[.visibility, .default_branch, (.security_and_analysis.secret_scanning.status // "n/a")] | @tsv'
gh api "repos/$OWNER/$REPO/actions/permissions/workflow" --jq '.default_workflow_permissions'   # read|write
gh api "repos/$OWNER/$REPO/actions/permissions"          --jq '.allowed_actions // "all"'         # all|local_only|selected
gh api "repos/$OWNER/$REPO/branches/$DEFAULT_BRANCH/protection" >/dev/null 2>&1 && echo yes || echo none
gh api "repos/$OWNER/$REPO/vulnerability-alerts"          >/dev/null 2>&1 && echo on  || echo off

Step 3: Severity model

  • WARN (fixable gap):
    • Dependabot alerts off
    • default_workflow_permissions = write (least-privilege violation; should be read)
    • a public repo with secret scanning not enabled
  • INFO (opinionated hardening — not a defect):
    • no branch protection on the default branch
    • allowed_actions = all

Step 4: Report

# Repo Security Audit — <owner> — <DATE>

> Generated by github-flow-kit/gh-repo-security-audit (OpenSSF-aligned)

| Repo | vis | def perms | allowed | branch prot | secret scan | Dependabot |
|---|---|---|---|---|---|---|
| <repo> | public | read | all | none | enabled | on |

## ⚠️ WARN (fixable): <N>
- <repo>: Dependabot alerts OFF
## ℹ️ INFO (hardening): <N>
- <repo>: no branch protection / allowed_actions=all

Step 5: Remediation

Safe, optional mutation — enable Dependabot alerts (only with --enable-dependabot; pure gain, reversible):

gh api -X PUT repos/<owner>/<repo>/vulnerability-alerts     # enable  (DELETE to undo)

Human-gated (never auto-applied) — print commands, let the user decide:

  • Token-Permissions: keep default read; declare per-workflow permissions: blocks in YAML.
  • Branch protection (esp. public + bot-PR repos): require reviews from someone other than the actor.
  • allowed_actionsselected + verified creators (stage rollout; third-party actions may break).
  • SHA-pin actions (uses: owner/action@<40-hex-sha>): add dependabot.yml github-actions ecosystem, or use ratchet/pin-github-action.
  • Review any pull_request_target / workflow_run workflows for untrusted PR-head checkout and ${{ github.event.* }} injection into run:.

Summary Output

✅ Repo Security Audit — <N> repos

  ⚠️ WARN (fixable) : <n>   (mostly Dependabot OFF — fix with --enable-dependabot)
  ℹ️ INFO (hardening): <n>
  ✅ secure          : <n>

📋 Next: --enable-dependabot for the safe fix; branch protection / allowed_actions / SHA-pin stay manual.

⭐ Found this useful? Star → https://github.com/thinkyou0714/github-flow-kit

Error Handling

CodeConditionExit
RS-001gh not authenticated2
RS-002owner has no repos0
RS-003per-repo API error (no admin / archived)skip that repo
RS-004API rate limitedstop, show reset time

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.