Add support for simple Gradle version catalog aliases

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
java, python

Research direction

Start in backend/app/scanners/analyzers/java.py to see how literal group:artifact:version Gradle declarations are extracted, then check the fixtures in backend/tests/scanners/test_java_analyzer.py. The change should read gradle/libs.versions.toml as data, resolve simple [libraries] aliases for implementation, api and test configurations, and leave anything unsupported unresolved. Done means the new fixture tests pass alongside the existing literal-parsing tests, and docs/languages.md describes the added support and its limits.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Summary

Gradle analysis currently extracts literal group:artifact:version declarations. Simple Gradle version catalog aliases in gradle/libs.versions.toml are not resolved, so dependencies referenced as implementation(libs.alias) or equivalent are missing from the inventory.

Affected files

  • backend/app/scanners/analyzers/java.py
  • backend/tests/scanners/test_java_analyzer.py
  • docs/languages.md

Scope

Read the conventional gradle/libs.versions.toml catalog and resolve simple library aliases used by supported dependency configurations. Parse the TOML as data only; never execute Gradle scripts or fetch artifacts. Leave unsupported expressions unresolved.

Acceptance criteria

  • The scanner reads gradle/libs.versions.toml when present.
  • Simple [libraries] aliases resolve from inline versions and version.ref entries.
  • Basic implementation(libs.alias), api(libs.alias), and test-configuration references are recognized.
  • Existing literal Gradle dependency parsing remains unchanged.
  • Complex expressions, unsupported catalog features, and unresolved version references remain unresolved rather than guessed.
  • Fixture-based tests cover inline versions, version.ref, supported configurations, unresolved expressions, and literal parsing.
  • docs/languages.md accurately documents the added catalog support and remaining limitations.

Testing expectations

Run the focused Java analyzer tests and relevant backend scanner tests. Confirm documentation claims match tested behavior.

Dominant language
Python
Stars
2
Forks
1
Avg merge
1h 22m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ayushdoesdev/verspect

All issues in ayushdoesdev/verspect

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.