How githubsecuritylab/gh-secure works
gh-secure is a GitHub CLI extension that helps maintainers enable or inspect repository security settings. The documented flow starts in a terminal or an AI assistant, invokes the extension, selects features (all by default, or explicitly), and applies or checks settings on a target repository. The README documents five distinct protections and interactive, unattended, dry-run, and status modes. Source excerpts were not available, so the graph reflects documented relationships only; feature implementation details and internal call structure remain unverified.
Main entry points: gh-secure gh-secure
Components 14
CLI workflow
- gh-secure
gh-secure - Interactive mode
gh-secure - Unattended mode
gh-secure - Dry run
gh-secure - Status check
gh-secure
Repository guardrails
- Branch protection
gh-secure - Secret scanning
gh-secure
Vulnerability defense
- Private reporting
gh-secure - Dependabot
gh-secure - Code scanning
gh-secure
GitHub platform
- GitHub CLI
- GitHub repository
Other components
- Maintainer
- AI assistant
Connections 18
- Maintainer → gh-secure: runs
README.md - AI assistant → gh-secure: invokes
README.md - gh-secure → GitHub CLI: extends
README.md - gh-secure → Interactive mode: offers
README.md - gh-secure → Unattended mode: offers
README.md - gh-secure → Dry run: offers
README.md - gh-secure → Status check: offers
README.md - gh-secure → Branch protection: enables
README.md - gh-secure → Secret scanning: enables
README.md - gh-secure → Private reporting: enables
README.md - gh-secure → Dependabot: enables
README.md - gh-secure → Code scanning: enables
README.md - Branch protection → GitHub repository: protects branches
README.md - Secret scanning → GitHub repository: scans secrets
README.md - Private reporting → GitHub repository: enables reporting
README.md - Dependabot → GitHub repository: checks dependencies
README.md - Code scanning → GitHub repository: scans code
README.md - Status check → GitHub repository: checks settings
README.md