release-manager
Pass
Audited by Gen Agent Trust Hub on Sep 8, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADSCOMMAND_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill ingests and processes git logs and commit messages from the repository environment. While this is necessary for its core functionality of generating changelogs and determining version bumps, it introduces a potential surface for indirect prompt injection if malicious instructions are embedded in commit history. * Ingestion points: Git logs (via stdin or text files) and release plan JSON files in
changelog_generator.pyandversion_bumper.py. * Boundary markers: The instructions do not define specific delimiters to isolate commit messages from agent processing. * Capability inventory: Scripts provided use standard libraries only; examples in documentation suggest integration with network and shell tools. * Sanitization: Commit messages are parsed via regular expressions to extract structured metadata. - [EXTERNAL_DOWNLOADS]: The documentation and example scripts reference external services including GitHub API and DataDog for release planning and monitoring notifications. * Evidence: Examples in
README.mdandhotfix-procedures.mduse therequestslibrary to interact withapi.github.comandapi.datadog.com. These are well-known services and their inclusion follows industry standard practices for DevOps automation. - [COMMAND_EXECUTION]: The skill documentation provides numerous examples of shell commands for version control and deployment management. * Evidence: Scripts like
release_planner.pyinclude command strings forkubectl, and theREADME.mdprovides examples usinggit,npm, anddocker. These are descriptive examples for user reference and are not executed automatically by the provided Python scripts.
Audit Metadata