More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Maven and Gradle Build Check

    1

    One maven { url "http://nexus..." } with allowInsecureProtocol = true lets anyone on the network swap the JARs your build runs, and nexusPassword=...

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Maven and Gradle Build Check

    Maven and Gradle Build Check

    Example session with this skill installed

    Check this project with maven-gradle-build-check.

    • Read your context and instructions
    • Compiled the maven and gradle

    $ python3 scripts/check_jvm_build.py examples/risky
    BLOCK inventory-api/.mvn/wrapper/maven-wrapper.properties:3 J03 WRAPPER_DOWNLOAD_OVER_HTTP
    distributionUrl=http://nexus.example.com/repository/maven-public/org/apache/maven/apache-maven/3.9.11/apache-maven-3.9.11-bin.zip
    Why: The Gradle or Maven wrapper (distributionUrl or wrapperUrl in gradle-wrapper.properties or maven-wrapper.properties, or the wrapper task in a build script) downloads the build tool over plain http://. Someone on the network can replace the distribution, and the wrapper then runs that code as your build tool on every machine that builds the project.
    Safer: Use https://services.gradle.org/distributions/... or https://repo.maven.apache.org/maven2/..., and add distributionSha256Sum so a changed download fails the build.

    BLOCK inventory-api/pom.xml:22 J01 INSECURE_REPOSITORY
    BLOCK inventory-api/pom.xml:60 J02 CREDENTIALS_IN_BUILD_FILE
    BLOCK reports-service/gradle.properties:5 J02 CREDENTIALS_IN_BUILD_FILE
    BLOCK reports-service/settings.gradle.kts:13 J01 INSECURE_REPOSITORY
    BLOCK reports-service/settings.gradle.kts:14 J01 INSECURE_REPOSITORY
    REVIEW inventory-api/.mvn/wrapper/maven-wrapper.properties:3 J15 WRAPPER_WITHOUT_CHECKSUM
    REVIEW inventory-api/pom.xml:16 J11 DYNAMIC_VERSION
    REVIEW inventory-api/pom.xml:24 J18 CHECKSUMS_IGNORED
    REVIEW inventory-api/pom.xml:38 J12 SNAPSHOT_DEPENDENCY
    REVIEW inventory-api/pom.xml:51 J16 PLUGIN_WITHOUT_VERSION
    REVIEW reports-service/build.gradle.kts:9 J17 REMOTE_BUILD_SCRIPT
    REVIEW reports-service/build.gradle.kts:14 J12 SNAPSHOT_DEPENDENCY
    REVIEW reports-service/gradle/libs.versions.toml:2 J11 DYNAMIC_VERSION
    REVIEW reports-service/settings.gradle.kts:3 J13 MAVEN_LOCAL_REPOSITORY
    REVIEW reports-service/settings.gradle.kts:11 J14 JCENTER_OR_BINTRAY

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 7 files, 7 with Maven or Gradle build content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    One maven { url "http://nexus..." } with allowInsecureProtocol = true lets anyone on the network swap the JARs your build runs, and nexusPassword=... in a committed gradle.properties lets anyone who reads the repository publish as you. This skill finds those and nine other Maven and Gradle build mistakes before you release, and tells you how to fix each one.

    Your agent runs a scanner on your pom.xml files, Maven settings.xml files kept in the project, Gradle build scripts in Groovy and Kotlin DSL (build.gradle, build.gradle.kts, settings.gradle, applied *.gradle scripts), gradle.properties, the Gradle and Maven wrapper properties and gradle/libs.versions.toml. It reads POMs as XML with line numbers and fills in ${properties}, skips Groovy and Kotlin comments, knows which strings Gradle fills in ("$nexusPassword") and the safe forms (${env.NAME}, encrypted Maven passwords, credentials(PasswordCredentials::class), mavenLocal() with a content filter), and leaves your own SNAPSHOT version and sibling modules alone. It never runs Maven, Gradle or the wrapper. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • J01: http:// repositories, mirrors and publishing targets, allowInsecureProtocol, scripts applied from http://, and settings.xml overrides of Maven's maven-default-http-blocker mirror
    • J02: passwords, tokens and signing keys written in build scripts, gradle.properties, POMs, settings.xml and repository or wrapper URLs (public Google Maps and Firebase keys are not reported)
    • J03: the Gradle or Maven wrapper downloaded over http://

    REVIEW

    • J11: dynamic versions: 1.+, latest.release, LATEST, RELEASE and version ranges
    • J12: SNAPSHOT dependencies, plugins and parent POMs from other groups
    • J13: mavenLocal() without a content filter
    • J14: jcenter() and Bintray repository URLs
    • J15: wrappers that download Gradle or Maven from a mirror or internal server without distributionSha256Sum
    • J16: Maven plugins without a version
    • J17: build scripts applied from an https:// URL
    • J18: Maven repositories with checksumPolicy ignore

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example project (a Maven service with the Maven wrapper, and a Gradle Kotlin DSL service with the wrapper, a version catalog and gradle.properties), and the real report the scanner produces on the risky one

    Limits It reads each file as written: parent POMs outside the scanned files, ~/.m2/settings.xml, ~/.gradle/gradle.properties, convention plugins in buildSrc or included builds, and values set on the command line or in CI are not followed, so a plugin version managed by a parent POM is trusted. .mvn/maven.config and Gradle dependency verification files are not read. NOT FLAGGED is not a guarantee.

    Static check of Maven and Gradle build file text. Parent POMs outside the scanned files, user-level Maven and Gradle settings, convention plugins and CI settings are not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example projects include clearly fake, inert passwords (NOTREAL-...) for the scanner to find. They are never run.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads pom.xml, build.gradle and related files as text. It never runs a build or downloads anything.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    New in Security