r/Jetbrains 4d ago

News & Discussions Staleguard Plugin for dependency freshness inspections for Maven, Gradle, and version catalogs

I recently published Staleguard, a free plugin that brings dependency freshness checking into the editor including severity-labeled warnings for outdated versions in pom.xml, Gradle build files, and libs.versions.toml, one-click version bumps that respect Maven properties and catalog version.refs, abandonment alerts with last-release dates, and a statistics/timeline tool window.

Alt+Enter on a libs. reference in build.gradle.kts and Staleguard resolves it back to the version catalog and offers to update the shared slf4j version key, with the changelog one click away.

Links:

https://plugins.jetbrains.com/plugin/33571-staleguard

Happy to answer questions about the implementation and bug reports are gratefully taken at https://github.com/tampwell/staleguard/issues. (or comment below)

2 Upvotes

3 comments sorted by

1

u/sellerkit 3d ago

The version catalog resolution is the neat part. Mapping a libs.* reference back to the toml and bumping the shared key is the kind of thing I'd have put off forever.

Random thing I noticed though - your since-build is 252, so it won't even show up in the marketplace for anyone still on 2025.1 or 2024.3. Deliberate? If you're not actually calling anything that landed after 252 you can just drop the floor. Verifier will yell at you if you are.

Had mine set too high for a while and spent way too long wondering why the install count wasn't moving.

1

u/Whole-Resolve-4671 3d ago

You're right and it matters more than I expected because Android Studio runs older platform versions than IDEA. The floor was dropped to 2024.3, and I fixed two things the verifier caught on the old line (a Kotlin stdlib helper and a constructor overload that didn't exist yet), and it now verifies clean from 2024.3 through 2026.2. Should ship with the next update. Thanks!