standards-gradle

Pass

Audited by Gen Agent Trust Hub on Feb 28, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill provides educational content focused on Gradle best practices without any malicious instructions or prompt injection attempts.\n- [SAFE]: It correctly identifies and warns against security risks such as hardcoding credentials and using insecure HTTP repositories, recommending the use of Gradle Properties and HTTPS instead.\n- [SAFE]: The included test project and Gradle wrapper (gradle-wrapper.jar and gradlew scripts) are standard components of a Gradle environment and show no signs of tampering or malicious behavior.\n- [SAFE]: Code examples involving network access (e.g., fetching a version string) use placeholder domains and are presented within the context of explaining Gradle build phases and lazy evaluation.
Audit Metadata
Risk Level
SAFE
Analyzed
Feb 28, 2026, 06:45 PM