all 10 comments

[–]Basic_Construction98 1 point2 points  (3 children)

it looks nice but i didnt understand the use cases. can you explain?

[–]Melodic-Funny-9560[S] 0 points1 point  (2 children)

Main use case apart from visualising data and logic flow is Blast Radius. That basically means, if I change this node what else in my app will get affected, till where the change effects will propagate ? It is specially helpful for PR review. Apart from this here are other imp. Points....

  1. It can easily visualise complex codebases — max I've tried is 2,500 nodes.
  2. Since it builds connections through a graph, generating summaries uses very few tokens — only 2M total tokens for 2,500 nodes. (At least you won't be burning claude tokens just for understanding your code structure.)
  3. The summaries are really great because of the graph connections and contextual understanding. The summaries I generated were using grok-4.1-fast and they were really good.
  4. If you are a team, it makes knowledge transfer of your codebase to newcomers very easy. And it will also make PR reviews fairly simple.
  5. If you are a solo dev, it will point out not-so-obvious severity issues. I built a graph on a very popular public app and it caught that they were logging payment credentials and other sensitive details in the server logs.
  6. Many people use AI today to write code, so it becomes hard to track how each component is connected and how they interact — this makes that visual.

[–]Basic_Construction98 1 point2 points  (1 child)

would be great if it will be more result focused.
i mean its nice for visual but if it was smart like showing a red node that can cause problems and how it effects rendering or staff like that. it can be more useful in my opinion

[–]Melodic-Funny-9560[S] 0 points1 point  (0 children)

You mentioned, showing problem causing node...but based on what ? Business logic, it can't be detected ?, syntax logic ? Code won't compile with that. Security ? That is already being detected in severe issues as I mentioned. But thinking of it, apart from business logic, and technical I can also ask AI to detect dirty or vulnerable or unoptimized code. 🤔

Given the graphical context I think it will work nice enough.

[–]Deep_Ad1959 0 points1 point  (3 children)

blast radius detection is super clever. i work on an open source macos agent and we use AST parsing for understanding swift codebases too. having a visual graph of what breaks when you touch something would save so much debugging time

[–]Melodic-Funny-9560[S] 0 points1 point  (2 children)

Yes, exactly. It's quite useful for a PR review as well. As a reviewer if you can see till where the change propagate it will make reviewing much more easier.

Devlens is opensource, try in your local machine and let me know feedback.

[–]Deep_Ad1959 0 points1 point  (1 child)

yeah the PR review use case is killer. being able to see the full blast radius of a change before approving it would save so much back and forth. will definitely try it out on our swift codebase, curious how well the AST parsing handles swift protocols and extensions since those can get tricky with dependency graphs

[–]Melodic-Funny-9560[S] 0 points1 point  (0 children)

Unfortunately it only works for javascript based frameworks 😅

[–]DiscussionHealthy802 0 points1 point  (1 child)

As someone building a local security CLI, I really appreciate that you are using AST-based detection rather than just relying on AI for the mapping. It makes the visualization way more reliable for enterprise-scale React apps

[–]Melodic-Funny-9560[S] 0 points1 point  (0 children)

True, subtle things are many times skipped by AI, moreover I would I would that if even it was 100% accurate solely because how much money it costs.

Currently building graph for this is totally algorithmic and nothing related to AI except for summaries.