110-java-maven-best-practices
Pass
Audited by Gen Agent Trust Hub on Sep 28, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill requires the execution of standard build commands including
mvn validate,mvn clean verify, and their respective Maven Wrapper (./mvnw) equivalents. These are used to ensure the project is in a valid state before modifications and to verify the integrity of the build after changes are applied. - [INDIRECT_PROMPT_INJECTION]: The skill acknowledges that project build files (
pom.xml) are untrusted external inputs. It implements a mitigation strategy by instructing the agent to use local XML tooling for structural extraction of specific allowlisted fields (e.g., coordinates, versions, dependencies) while explicitly prohibiting the ingestion or processing of free-text fields such as descriptions, names, and comments that could contain malicious instructions. - Ingestion points: Project
pom.xmlfiles, including root and child modules. - Boundary markers: Explicit instructions are present requiring the agent to treat POM contents as untrusted and ignore embedded free-text instructions.
- Capability inventory: The skill utilizes file reading and execution of the Maven CLI toolset.
- Sanitization: Involves allowlisted structural extraction of Maven metadata using local XML processing APIs rather than full file ingestion.
- [SAFE]: No instances of obfuscation, hardcoded credentials, unauthorized data exfiltration, or malicious persistence mechanisms were detected. The skill follows developer best practices by defining clear constraints and validation steps.
Audit Metadata