rudder-typer-workflow
Pass
Audited by Gen Agent Trust Hub on Oct 28, 2026
Risk Level: SAFEEXTERNAL_DOWNLOADSINDIRECT_PROMPT_INJECTION
Full Analysis
- [EXTERNAL_DOWNLOADS]: The CI/CD integration guide in
references/ci-cd-integration.mdincludes a workflow that downloads therudder-clibinary from the vendor's official GitHub repository. This is a standard operation for setting up the required tooling. - Evidence:
curl -fsSLO "https://github.com/rudderlabs/rudder-iac/releases/download/$tag/rudder-cli_Linux_x86_64.tar.gz"inreferences/ci-cd-integration.md. - Security Practice: The installation script implements a security best practice by verifying the downloaded archive against an official checksum file using
sha256sumbefore extraction. - [INDIRECT_PROMPT_INJECTION]: The skill processes external tracking plan data (YAML) to generate code, which is a potential surface for indirect injection if the source data is untrusted.
- Ingestion points: Local files like
tracking-plan.yamlandruddertyper.ymlas described inSKILL.md. - Boundary markers: Not explicitly defined in the instructions, though the
rudder-clitool performs validation on the input schema. - Capability inventory: The skill uses
rudder-clito validate plans, apply changes to a remote workspace, and generate source code (Swift/Kotlin). It also utilizes standard file read/write/edit tools. - Sanitization: Relies on the internal validation logic of the
rudder-clitool; the skill itself does not specify additional sanitization steps for the input data.
Audit Metadata