I recently released Library Insight v1.1.0. It's a...

# feed

[Meet]

I recently released Library Insight v1.1.0.
It's an open-source CLI for exploring Java/Kotlin libraries without needing their source code. It scans JARs, AARs, or Maven coordinates and builds a searchable API index from the compiled bytecode.
In this release I focused on making it more useful for everyday development and AI-assisted workflows.
What's new in v1.1.0
• MCP Server – AI clients like Cursor or Claude Desktop can interact with Library Insight through the Model Context Protocol instead of manually running CLI commands.
• Migration Advisor – Compare two library versions to see added, removed, and deprecated APIs when upgrading dependencies.
• Dependency API Audit – Scan Gradle dependencies and report deprecated APIs found in the actual library bytecode.
• Dependency Graph – Visualize transitive dependencies directly from Maven artifacts.
• Search Maven Central – Find Maven coordinates and available versions from the terminal.
• SemVer Checker – Compare API changes with version numbers to identify potential Semantic Versioning mismatches.
I also simplified the documentation, added a shorter demo script, and reorganized the command reference to make the project easier to get started with.
I'm not sure how useful this will be for others, so I'd really appreciate any feedback, suggestions, or feature ideas.
GitHub: github.com/Coding-Meet/Library-Insight
Doc: coding-meet.github.io/Library-Insight

[Michal Harakal]

This looks really useful, I’d like to try it, but wanted to ask first whether you have any experience with libraries that expose Kotlin DSLs. The library I’m working on is heavily DSL based, so I’m curious how well Library Insight handles extension functions, builders, receivers, and generated APIs?

[Meet]

Thanks! I haven't tested it yet on a DSL library, so I can't claim complete coverage. However, Library Insight does parse Kotlin @Metadata in addition to JVM bytecode, so it can extract Kotlin-specific information such as extension functions, extension receivers, default arguments, suspend, inline, operator, and infix modifiers where that metadata is available.

If you're open to trying it with your library, I'd really appreciate your feedback. If you run into any cases where Library Insight doesn't handle the DSL correctly, feel free to open an issue or let me know. It'll help me improve support for those cases in future releases.

[Meet]

yes i try add dsl in next release

[Meet]

I not understand my cli project not see it developer may be not understand i don't know

[Meet]

Any idea

[Michal Harakal]

I think Kotlin DSL support is slightly different from simply extracting Kotlin API metadata. A DSL is an abstraction created by several API elements working together, such as extension functions, lambda receivers, builders, nested scopes, annotations, and generated types. Looking at each element separately may show what exists, but not necessarily how the library author expects developers to combine them.
That makes me wonder how I, as a library author, can provide this missing context to Library Insight. For example, could it consume KDoc examples, Dokka module or package Markdown files, README examples, or some structured metadata bundled with the library? That would allow the tool or an AI agent to understand not only the available API, but also the intended entry points, valid nesting, typical usage patterns, and relationships between the DSL components.

[Meet]

That's actually a good point. Until now I've mostly focused on extracting everything that's available from the compiled library itself. I hadn't really thought about using documentation as an additional source of context.
I can definitely see how KDoc, Dokka pages, or even README examples could help explain how the DSL is actually intended to be used, not just what APIs exist. I'll explore that direction. Thanks for the suggestion!

[Meet]

i added v1.2.0 not release but you can check

github.com/Coding-Meet/Library-Insight/blob/…/CLI.md

[Meet]

Currently rewrite documention and website so developer may be understood how can use it what are issue faced how can fix it

[Meet]

i think on better understand
https://coding-meet.github.io/Library-Insight/

[Michal Harakal]

Hi, I was testing Library Insight with my lib. As a result you have 4 PRs (with a little help of Claude). I consider them useful, otherwise I wouldn't waste your and my time, but feel free to reject or just close.

[Meet]

Thanks a lot! I really appreciate you trying Library Insight with your library and taking the time to open those PRs. I'll review them when I get some free time. If they fit the project, I'll be happy to merge them. Thanks again for contributing!

[Meet]

Also, if you think of any features that would make Library Insight more useful for your library or workflow, feel free to create an issue. I'll do my best to add support for them if they fit the project.

[Michal Harakal]

Yes, github.com/Coding-Meet/Library-Insight/pull/5 is a significant new feature. Maybe I should have created an issue before implementing it.

[Meet]

Thanks I will check

[Meet]

v1.2.0 release it
Doc: coding-meet.github.io/Library-Insight
GitHub: github.com/Coding-Meet/Library-Insight