github/safe-settings — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2026-06-18
Enforce consistent branch protection and security policy across hundreds of repositories from one config.
Automatically revert manual GitHub settings changes that conflict with organization policy.
Preview policy-file pull requests with a dry-run before the changes take effect.
Let individual teams override organization-wide defaults for their own repositories.
| github/safe-settings | namastedev/namaste-react | justjavac/chromesnifferplus | |
|---|---|---|---|
| Stars | 880 | 858 | 847 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | 2026-06-18 | — | — |
| Maintenance | Active | — | — |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 1/5 | 1/5 |
| Audience | ops devops | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires deploying a GitHub App and setting up an admin repo with YAML policy files.
Safe-Settings is a GitHub app that lets you manage branch protection, team access, and security policy for an entire organization from one config file, then automatically enforces and re-syncs it across every repo.
Mainly JavaScript. The stack also includes JavaScript, YAML, GitHub App.
Active — commit in last 30 days (last push 2026-06-18).
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.