glab-docs
Pass
Audited by Gen Agent Trust Hub on Sep 18, 2026
Risk Level: SAFEREMOTE_CODE_EXECUTIONPERSISTENCEPRIVILEGE_ESCALATIONDYNAMIC_EXECUTIONMETADATA_POISONING
Full Analysis
- [REMOTE_CODE_EXECUTION]: The documentation references commands like
glab orbitandglab duo clithat download and execute binaries from GitLab infrastructure. It also includes instructions for installing the tool via third-party repositories, such as executing a script fromupciti/wakemeopsusingcurl | sudo bash. - [PERSISTENCE]: The documentation provides instructions for configuring shell completions for various shells, which involve appending load commands to shell profile files like
~/.zshrc. - [PRIVILEGE_ESCALATION]: The documentation describes operations requiring elevated permissions, such as system-wide completion installation in
/etc/bash_completion.d/and granting filesystem access to the system keychain for authentication in sandboxed environments. - [DYNAMIC_EXECUTION]: The documentation explains the
valueFromCommandconfiguration setting, which allows theglabCLI to execute user-defined shell commands to generate dynamic HTTP header values. - [METADATA_POISONING]: The skill metadata labels the content as the "Official command reference for glab," although the skill is maintained by a community contributor ('wenerme') rather than the official GitLab organization.
Audit Metadata