jenkins-pipelines

Pass

Audited by Gen Agent Trust Hub on May 24, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill encourages the use of the withCredentials block for handling secrets, which is the recommended security practice for Jenkins pipelines to avoid hardcoding credentials.
  • [SAFE]: The pipeline templates include operational safeguards such as timeout to prevent hung processes and cleanWs() to ensure workspace hygiene.
  • [SAFE]: The provided Kubernetes agent configuration includes a privileged container for Docker-in-Docker operations; while high-privilege, this is a standard and expected pattern for image building within containerized CI/CD environments.
  • [SAFE]: Instructions correctly advise on the use of shared libraries for common code and Jenkins Configuration as Code (JCasC) to maintain a secure and auditable infrastructure.
  • [SAFE]: The skill exhibits an indirect prompt injection surface by using environment variables like GIT_COMMIT and BRANCH_NAME in shell interpolation (sh "... --set image.tag=${GIT_COMMIT.take(8)}"); however, this is standard CI/CD practice and the templates provided do not implement malicious functionality.
Audit Metadata
Risk Level
SAFE
Analyzed
May 24, 2026, 03:10 PM
Security Audit — agent-trust-hub — jenkins-pipelines