Git protection
Reviews everyday Git porcelain plus local and remote operations that can discard work, replace history, refresh a remote Guard cannot verify
Evidence at a glance
- Source
- Merged native coverage · f440ae1a9f
- Activation
- This coverage is part of Guard’s required safety floor.
- Maintainer
- Project maintained
- Coverage
- 39 rules · 39 permissions
Coverage and limits
Reviews everyday Git porcelain plus local and remote operations that can discard work, replace history, refresh a remote Guard cannot verify, or read a staged index Guard cannot bound.
- Coverage is limited to the reviewed operations and the surrounding Guard policy.
- A maintainer profile is not a security certification or an official upstream endorsement.
Command mapping and enforcement
How Guard maps this extension onto your workspace policy: which commands it recognizes, which tools it touches, and how each tool state resolves.
Runtime identity
- Catalog ID
command.git- Guard enforcement ID
command.git- Source path
src/codex_plugin_scanner/guard/runtime/command_builtin_extension_registry.py
Tool state mapping
No per-tool overrides are declared. Every tool this extension touches resolves through the workspace Guard policy as-is.
Action classes
git destructive commandgit origin refreshgit index inspectiongit workspace commandgit read commandFrequently asked questions
What does Git protection cover?
Reviews everyday Git porcelain plus local and remote operations that can discard work, replace history, refresh a remote Guard cannot verify, or read a staged index Guard cannot bound. The listing declares 39 rules and 39 permission checks. Coverage is limited to these reviewed operations and the surrounding Guard policy.
Is Git protection active by default?
Required protection: This coverage is part of Guard’s required safety floor. Enabling state is always controlled through Guard policy, never from this directory.
Who maintains Git protection?
This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.
Is a listing of Git protection a security guarantee?
No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.