Skip to content

h4x0r/1-click-github-sec

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

1-Click GitHub Security πŸ›‘οΈ

1-Click GitHub Security

Deploy security controls to any project in one command

Security that auto-fixes problems instead of just complaining about them

Created by Albert Hui albert@securityronin.com LinkedIn Website

Supports Rust, Node.js, Python, Go, and generic projects with 35+ security controls including pre-push validation, CI/CD workflows, and GitHub security features.

πŸ“Š Executive Briefing | πŸ“š Documentation | πŸ—οΈ Architecture

Security GitHub Integration GitHub Security Performance License Version


🎯 What You Get

Pre-Push Security (< 60 seconds)

βœ… Secret detection - Blocks API keys, passwords, tokens βœ… Vulnerability scanning - Catches known security issues βœ… Code quality checks - Language-specific linting βœ… Test validation - Ensures tests pass before push βœ… Supply chain security - SHA pinning, dependency validation

CI/CD Workflows (Comprehensive Analysis)

πŸ” Static analysis - SAST with CodeQL and Trivy πŸ” Dependency auditing - Automated vulnerability detection πŸ” Security reporting - SBOM generation and metrics πŸ” Compliance checking - License and policy validation

GitHub Security Features (Automated Setup)

πŸ€– Renovate - Automated dependency updates with automerge πŸ” Secret scanning - Repository-wide credential detection πŸ” Branch protection - Enforce security policies πŸ” Security advisories - Vulnerability disclosure workflow


🧠 Design Philosophy: Don't Make Me Think (DMMT)

Security that works like a UK power plug - impossible to do wrong, automatic to do right.

Our DMMT principle means:

  • πŸ›  Auto-fixes instead of errors - We fix SHA pinning automatically, not just complain
  • ⚑ Zero configuration required - Sensible defaults that work immediately
  • 🎯 One command, comprehensive security - No manual setup or integration
  • ✨ Invisible when working - Security runs in background, visible only when needed
  • πŸ”§ Graceful degradation - Partial features better than complete failure

Example: Instead of "Error: Action not pinned", you see "βœ… Auto-pinned actions/checkout@v4 β†’ @08eba0b2"

This isn't just convenient - it's security through design. Like the UK plug that physically prevents incorrect insertion, we make insecure practices impossible rather than merely discouraged.


πŸš€ Quick Start

Install security controls in your project:

# Download installer and SLSA provenance
curl -O https://github.com/h4x0r/1-click-github-sec/releases/download/v0.7.0/install-security-controls.sh
curl -O https://github.com/h4x0r/1-click-github-sec/releases/download/v0.7.0/multiple.intoto.jsonl

# VERIFY with SLSA provenance (cryptographic proof of authenticity)
# Install slsa-verifier: https://github.com/slsa-framework/slsa-verifier#installation
slsa-verifier verify-artifact \
  --provenance-path multiple.intoto.jsonl \
  --source-uri github.com/h4x0r/1-click-github-sec \
  install-security-controls.sh

# Install after verification
chmod +x install-security-controls.sh
./install-security-controls.sh

Python projects: Activate your environment first for optimal tool installation:

# conda/miniconda
conda activate myproject

# pyenv/asdf/mise
pyenv local 3.11.0  # or: mise use python@3.11

# virtual environment
source venv/bin/activate

# Then run installer
./install-security-controls.sh

That's it! Your project now has comprehensive security controls with cryptographic verification!

No configuration files to edit. No tools to manually install. No documentation to read. It just works.

Why verify? Every release is cryptographically signed with SLSA Build Level 3 provenance - proving it wasn't tampered with. Learn more β†’


πŸ“– Complete Documentation

πŸ‘‰ Visit Documentation Site πŸ‘ˆ

πŸš€ New Users

πŸ”§ Power Users

πŸ‘₯ Contributors

πŸ“Š Leadership


πŸ“Š This Repository vs Your Project

This repository demonstrates "dogfooding plus" - it uses enhanced security controls beyond what it installs:

Feature What Installer Gives You What This Repository Has
Pre-push Controls 24 universal security checks 24 security checks + 5 development-specific
CI/CD Workflows Optional installation 6 specialized development workflows
GitHub Security Automated setup Enhanced with custom policies
Documentation Installation guides Complete documentation site + development controls documentation
Cryptographic Signing Optional setup All commits & releases signed

Bottom line: We use an enhanced version of what we provide to others, proving it works in production.


πŸ’¬ Support & Community


πŸ“„ License

Licensed under the Apache License, Version 2.0. See LICENSE for details.


πŸ›‘οΈ Secure by default. Simple by design. Verified by cryptography.

About

One-click install basic security controls for GitHub-managed projects

Topics

Resources

License

Code of conduct

Contributing

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages