easy4j-deploy
Pass
Audited by Gen Agent Trust Hub on Aug 19, 2026
Risk Level: SAFECOMMAND_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
- [COMMAND_EXECUTION]: The skill utilizes local shell scripts to automate project release cycles, involving Git and Maven operations.
- Evidence: The scripts
scripts/release-sdk.shandscripts/release-starter.shmanage the end-to-end release process, including version bumping, tagging, and deployment to Maven Central. - [EXTERNAL_DOWNLOADS]: The skill interacts with established software registries and security services for dependency validation and metadata retrieval.
- Evidence:
scripts/cve-scan.shperforms automated vulnerability lookups by queryinghttps://api.osv.dev/v1/querybatch. - Evidence: The dependency management guidelines in
references/dependency-matrix.mdutilizecurlto verify artifact availability onrepo1.maven.organdmaven.aliyun.com. - [REMOTE_CODE_EXECUTION]: A localized Python execution is used for processing JSON data within the scanning script.
- Evidence:
scripts/cve-scan.shpipes the output of a network request intopython3 -cusing a static, hardcoded parsing script. This does not involve executing arbitrary code from a remote source. - [INDIRECT_PROMPT_INJECTION]: The skill processes project configuration files (
pom.xml) which could theoretically contain malicious data, though the risk is mitigated by specific parsing logic. - Ingestion points: Automated parsing of version strings and property tags from the local
pom.xmlfile. - Capability inventory: The agent has the authority to execute shell commands, perform builds, and push changes to remote Git branches.
- Boundary markers: The scripts use specific XML tag matching (via
grepandperl) to isolate version data from other file content. - Sanitization: Extracted version strings are used as arguments to Maven and Git commands, with the logic restricted to expected semantic versioning patterns.
Audit Metadata