docs: update license scanning support

[zhamborova]

Summary

Updates the supported languages and tools page to document license scanning availability by ecosystem. The license scanning column now names the supported ecosystem directly, while the existing Trivy scan details remain in the dependency vulnerability and malicious packages detection columns.

Ecosystem to language mapping:

• Gem -> Ruby
• Cargo -> Rust
• Composer -> PHP
• Conan -> C, C++
• Go modules -> Go
• Hex -> Elixir
• Maven -> Java, Kotlin, Scala
• npm -> JavaScript, TypeScript
• NuGet -> C#
• Pub -> Dart
• PyPI -> Python
• SwiftPM -> Swift

Validation

• mkdocs build --strict
• Parsed the supported languages table and confirmed every row has the expected number of cells
• Checked for unresolved conflict markers and whitespace errors

[gemini-code-assist]

Code Review

This pull request updates the documentation in docs/getting-started/supported-languages-and-tools.md to highlight the addition of license scanning as a supported feature. It also updates the language support table to clearly state the availability of license scanning for various package managers (such as Conan, NuGet, Pub, Go modules, Maven, npm, Composer, PyPI, Bundler, Cargo, and SwiftPM) instead of using dashes or specific tool scan details. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[github-actions]

Overall readability score: 54.23 (🟢 +0)

File	Readability
supported-languages-and-tools.md	49.15 (🟢 +0)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
supported-languages-and-tools.md	49.15	31.17	10.81	13.1	14.2	7.81
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	54.23	43.16	10.9	12.3	12.24	8.01
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[codacy-production]

Pull Request Overview

Codacy analysis indicates that the PR is up to standards. The changes successfully implement the 'Available for [Ecosystem]' terminology across the supported languages table. However, cross-correlation with the Intent agent's acceptance criteria and the existing documentation structure reveals significant implementation gaps. By standardizing the entries, technical specificity has been lost for Java, JavaScript, and Python ecosystems. Most notably, the updates create internal inconsistencies by failing to mention Gradle and Yarn support which are listed in the 'Dependency Scanning' columns for the same languages. These regressions in documentation detail should be addressed to maintain the document's utility.

About this PR

• The standardization to 'Available for [Ecosystem]' has introduced technical gaps. Several languages (e.g., Java and JavaScript) support multiple package managers like Gradle and Yarn which are now omitted from the License Scanning column, despite being documented in the Dependency Scanning column. This creates a discrepancy that may confuse users regarding the actual scope of license scanning support.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}