GitLab CI/CD command protection
Reviews remote pipeline cancellation through GitLab CLI.
Evidence at a glance
- Source
- Merged native coverage · f440ae1a9f
- Activation
- This coverage is built into the native Guard runtime.
- Maintainer
- Project maintained
- Coverage
- 1 rules · 1 permissions
Coverage and limits
Reviews remote pipeline cancellation through GitLab CLI.
- 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.cicd.gitlab- Guard enforcement ID
command.cicd.gitlab- 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
GitLab pipeline administrative commandFrequently asked questions
What does GitLab CI/CD command protection cover?
Reviews remote pipeline cancellation through GitLab CLI. The listing declares 1 rule and 1 permission check. Coverage is limited to these reviewed operations and the surrounding Guard policy.
Is GitLab CI/CD command protection active by default?
Built-in coverage: This coverage is built into the native Guard runtime. Enabling state is always controlled through Guard policy, never from this directory.
Who maintains GitLab CI/CD command protection?
This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.
Is a listing of GitLab CI/CD command 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.