gradle-best-practices
Pass
Audited by Gen Agent Trust Hub on Oct 1, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill possesses an indirect prompt injection surface because it processes untrusted Gradle build scripts and properties files from a user's project and has the capability to modify source code.\n
- Ingestion points: Step 1 in SKILL.md discovered and reads all Gradle-related files in a project, including build.gradle, settings.gradle, and gradle.properties.\n
- Boundary markers: The instructions do not define explicit boundary markers or safety instructions for the agent to ignore prompts embedded in the project files being audited.\n
- Capability inventory: The skill is capable of modifying files through Step 6 ("Apply fixes"), which allows the agent to propose and execute code changes in build scripts and configuration files.\n
- Sanitization: There is no evidence of sanitization or escaping of the processed build file content before it is interpolated into the agent's reasoning cycle.\n- [SAFE]: The skill follows security best practices for AI agents by bundling its reference catalog locally and forbidding network operations at runtime. It is authored by the official vendor (gradle) and uses official documentation URLs from trusted domains (gradle.org, services.gradle.org).
Audit Metadata