Eshwar Prasad Yaddanapudi

founder & Open Source Blast Radius and Lineage for @servicenow #Fluent applications.

[Eshwar Prasad Yaddanapudi @yesprasad26]

Someone should ask @Gartner_inc why there's no quadrant for system understanding in AI-assisted development. Because there's already a leader. #FluentGraph for @ServiceNow #Fluent #BuiltWithFluent
@ServiceNowNews @ServiceNowRSRCH

[Eshwar Prasad Yaddanapudi @yesprasad26]

Agreed! Great point. thanks for bringing up this buddy.
yes, Today LOW is a lower bound on the resolved static graph, not a proof of safety.

We should make that explicit. The next step is to surface opaque call/import sites and carry a coverage state, so unresolved behavior produces PARTIAL / UNKNOWN rather than a falsely reassuring LOW.

[Eshwar Prasad Yaddanapudi @yesprasad26]

🔥🔥Introducing deep-graph - "Beyond the diff"

AI code review tools read your diff.
They don't know what depends on what you changed.

I built deep-graph — an open-source CLI that resolves blast radius through the TypeScript type system.

Change one file → see every module affected, across imports, re-exports, and path aliases on any @typescript repos.

Ships as an MCP server so @claudeai , @cursor_ai , and #GitHubCopilot or any code Review tool can query it directly.

npm i -g @yesprasad/deep-graph

https://t.co/5u4wIdOgvH

[Eshwar Prasad Yaddanapudi @yesprasad26]

@DhravyaShah @supermemory would love to see your observations for #DeepGraph It helps your AI Code Review tools get deeper understanding of cross-articats and cross-file references and implications for @typescript repos. Let me know if I can be of some help running this.

[Ramchand Kumaresan @Mechramc]

Spent an hour today poking at deep-graph, a little CLI Eshwar Prasad put up this week.

The pitch is simple: before you change a file, ask what breaks. Most tools answer that by grepping imports. This one actually spins up the TypeScript compiler and asks the type checker, so aliases, barrel files and cross-file calls resolve the way "go to definition" does instead of the way a regex guesses.

I ran it on tmy Storyforge Kids repo. Pointed it at our supabase client and it came back in about 2.5 seconds with 30 things that depend on it, down to which function calls which. I checked a handful by hand and they were all right.

There's an MCP server too, so Claude Code can ask "what's the blast radius here" before it edits. That's the part I'm actually keeping. I dropped a .mcp.json into the repo and I'm going to make the agent run it before touching anything shared. Our types.ts is imported by 28 files and I'd rather know that before a refactor than after.

Couple of rough edges since it's a 0.1: TypeScript only for now. But if you're letting an AI review or edit your code, this is the context a diff doesn't have. Worth a look.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@huntlovell Hi @huntlovell, just sent you a DM. Hope you would have a look and respond me. thanks.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@zdogmode no - because the probability distribution and inherent non-determinism and context makes a difference

[Eshwar Prasad Yaddanapudi @yesprasad26]

@coryalthoff https://t.co/5vwC05cF6A

[Eshwar Prasad Yaddanapudi @yesprasad26]

@DhravyaShah crazy dude - love it

[Eshwar Prasad Yaddanapudi @yesprasad26]

@DanielLockyer https://t.co/5vwC05cF6A

[Eshwar Prasad Yaddanapudi @yesprasad26]

@catmanyau - Yes! it does - It resolves static import/export/re-export and path-alias edges, then traverses them transitively. blast-pr command returns a ranked impact map (changed file → affected artifacts, depth, risk) rather than only files touched. feel free to try it
https://t.co/9MXfBs90LC and pass on your observations.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@bert_programmer Bert, the code is OSS on github - https://t.co/yK6knBV9Hw star it and use it and help me with your observations. would love to see #DeepGraph be of help to fellow @typescript devs like me.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@Mechramc Thank you @Mechramc for your valuable feedback and observations. means a lot to me.

[Eshwar Prasad Yaddanapudi @yesprasad26]

Thank you @Mechramc for using #DeepGraph in project. I am happy it is adding value to your @typescript repos. I will take your feedback and suggestions and improve it. Initial release getting this observations is a happy case for me. Means a lot. Thank you again for sharing your insights.

[Ramchand Kumaresan @Mechramc]

Spent an hour today poking at deep-graph, a little CLI Eshwar Prasad put up this week.

The pitch is simple: before you change a file, ask what breaks. Most tools answer that by grepping imports. This one actually spins up the TypeScript compiler and asks the type checker, so aliases, barrel files and cross-file calls resolve the way "go to definition" does instead of the way a regex guesses.

I ran it on tmy Storyforge Kids repo. Pointed it at our supabase client and it came back in about 2.5 seconds with 30 things that depend on it, down to which function calls which. I checked a handful by hand and they were all right.

There's an MCP server too, so Claude Code can ask "what's the blast radius here" before it edits. That's the part I'm actually keeping. I dropped a .mcp.json into the repo and I'm going to make the agent run it before touching anything shared. Our types.ts is imported by 28 files and I'd rather know that before a refactor than after.

Couple of rough edges since it's a 0.1: TypeScript only for now. But if you're letting an AI review or edit your code, this is the context a diff doesn't have. Worth a look.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@VaraadDurgaay Thanks for your kind words Varad.

[Govinda_lll @govindalllonx]

there's an AI video that shows Hampi before attacked by Islamic invaders

[Eshwar Prasad Yaddanapudi @yesprasad26]

@supermemory lets integrate with DeepGraph

[Eshwar Prasad Yaddanapudi @yesprasad26]

@Joshua_WD Thank you Josh. Yes - enterprise systems need trust and reliability. #DeepGraph brings them to make teams deploy with confidence.

[Eshwar Prasad Yaddanapudi @yesprasad26]

🔥🔥Introducing deep-graph - "Beyond the diff"

AI code review tools read your diff.
They don't know what depends on what you changed.

I built deep-graph — an open-source CLI that resolves blast radius through the TypeScript type system.

Change one file → see every module affected, across imports, re-exports, and path aliases on any @typescript repos.

Ships as an MCP server so @claudeai , @cursor_ai , and #GitHubCopilot or any code Review tool can query it directly.

npm i -g @yesprasad/deep-graph

https://t.co/5u4wIdOgvH

[Eshwar Prasad Yaddanapudi @yesprasad26]

@BhoomiSinghani - introducing deep-graph - make code review tools do better than diffs. deep-graph lets you avoid costly hidden failures early. I will see you at the next @Devlabs_club with metrics.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@DhravyaShah @supermemory @sohamdaga22 a lot of points that we discussed are now part of deep-graph.

[Eshwar Prasad Yaddanapudi @yesprasad26]

@DhravyaShah here is deep-graph - try it on @supermemory repo whenever there is a PR. it works like a charm.